Bug 111076

Summary: Building error after commit b52bf8f12a ("amd/common/gfx10: support new tbuffer encoding")
Product: Mesa Reporter: Mauro Rossi <issor.oruam>
Component: Drivers/Gallium/radeonsiAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED MOVED QA Contact: Default DRI bug account <dri-devel>
Severity: critical    
Priority: medium    
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: other   
Whiteboard:
i915 platform: i915 features:

Description Mauro Rossi 2019-07-06 16:03:57 UTC
Hi,

I'm getting the following building error, even if I'm using prescribed LLVM8
and libdrm 2.4.99:

external/mesa/src/amd/common/ac_llvm_build.c:1496:45: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_8_UINT'
                case V_008F0C_BUF_DATA_FORMAT_8: format = V_008F0C_IMG_FORMAT_8_UINT; break;
                                                          ^
external/mesa/src/amd/common/ac_llvm_build.c:1497:47: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_8_8_UINT'
                case V_008F0C_BUF_DATA_FORMAT_8_8: format = V_008F0C_IMG_FORMAT_8_8_UINT; break;
                                                            ^
external/mesa/src/amd/common/ac_llvm_build.c:1498:51: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_8_8_8_8_UINT'
                case V_008F0C_BUF_DATA_FORMAT_8_8_8_8: format = V_008F0C_IMG_FORMAT_8_8_8_8_UINT; break;
                                                                ^
external/mesa/src/amd/common/ac_llvm_build.c:1499:46: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_16_UINT'
                case V_008F0C_BUF_DATA_FORMAT_16: format = V_008F0C_IMG_FORMAT_16_UINT; break;
                                                           ^
external/mesa/src/amd/common/ac_llvm_build.c:1500:49: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_16_16_UINT'
                case V_008F0C_BUF_DATA_FORMAT_16_16: format = V_008F0C_IMG_FORMAT_16_16_UINT; break;
                                                              ^
external/mesa/src/amd/common/ac_llvm_build.c:1501:55: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_16_16_16_16_UINT'
                case V_008F0C_BUF_DATA_FORMAT_16_16_16_16: format = V_008F0C_IMG_FORMAT_16_16_16_16_UINT; break;
                                                                    ^
external/mesa/src/amd/common/ac_llvm_build.c:1502:46: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_32_UINT'
                case V_008F0C_BUF_DATA_FORMAT_32: format = V_008F0C_IMG_FORMAT_32_UINT; break;
                                                           ^
external/mesa/src/amd/common/ac_llvm_build.c:1503:49: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_32_32_UINT'
                case V_008F0C_BUF_DATA_FORMAT_32_32: format = V_008F0C_IMG_FORMAT_32_32_UINT; break;
                                                              ^
external/mesa/src/amd/common/ac_llvm_build.c:1504:55: error: use of undeclared identifier 'V_008F0C_IMG_FORMAT_32_32_32_32_UINT'
                case V_008F0C_BUF_DATA_FORMAT_32_32_32_32: format = V_008F0C_IMG_FORMAT_32_32_32_32_UINT; break;
                                                                    ^
9 errors generated.

Could you please check if some include is missing or what library is supposed to provide those definitions?

Mauro
Comment 1 Mauro Rossi 2019-07-06 16:04:44 UTC
I'm building Android (pie-x86)
Mauro
Comment 2 Mauro Rossi 2019-07-06 20:21:37 UTC
The problem is missing changes in android building rules with gfx10

I have submitted series of patches to mesa-dev that fix the problem
Mauro
Comment 3 GitLab Migration User 2019-09-25 18:50:13 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/1414.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.