Bug 47881 - r600_asm.c:780:12: internal compiler error with gcc-4.7.0
Summary: r600_asm.c:780:12: internal compiler error with gcc-4.7.0
Status: RESOLVED NOTOURBUG
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/R600 (show other bugs)
Version: 8.0
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-26 00:47 UTC by treeve
Modified: 2012-03-26 00:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description treeve 2012-03-26 00:47:38 UTC 
using gcc-4.7.0, I get the following  error when compiling Mesalib-8.0.2


changing optimisation to -O2 works


root@Gemini-64:/usr/src/Mesa-8.0.2/src/gallium/drivers/r600# make
gcc -c -I. -I../../../../src/gallium/include -I../../../../src/gallium/auxiliary -I../../../../src/gallium/drivers -I../../../../include -march=native -mtune=native -m64 -pipe -O3 -Wall -Wmissing-prototypes -std=c99 -fno-strict-aliasing -fno-builtin-memcmp -march=native -mtune=native -m64 -pipe -O3  -fPIC  -DUSE_X86_64_ASM -D_GNU_SOURCE -DPTHREADS -DHAVE_POSIX_MEMALIGN -DUSE_XCB -DGLX_INDIRECT_RENDERING -DGLX_DIRECT_RENDERING -DUSE_EXTERNAL_DXTN_LIB=1 -DIN_DRI_DRIVER -DHAVE_ALIAS -DHAVE_MINCORE -DHAVE_LIBUDEV -DHAVE_XCB_DRI2 -D__STDC_CONSTANT_MACROS -DHAVE_LLVM=0x0300 -fvisibility=hidden -I/usr/include    -D_GNU_SOURCE   -Wno-unused-parameter -Wwrite-strings  -Wno-long-long -D__STDC_CONSTANT_MACROS -D__STDC_FORMAT_MACROS -D__STDC_LIMIT_MACROS r600_asm.c -o r600_asm.o
r600_asm.c: In function 'check_and_set_bank_swizzle':
r600_asm.c:780:12: internal compiler error: in try_move_mult_to_index, at fold-const.c:6995
Please submit a full bug report,
with preprocessed source if appropriate.
Comment 1 Michel Dänzer 2012-03-26 00:51:22 UTC 
An internal compiler error is a compiler bug. Please report this to GCC.

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.