| Summary: | [regression] failure in building nvc0_vbo.lo: /tmp/cclDjdRp.s:1270: Error: missing or invalid displacement expression `-8589934576 | ||
|---|---|---|---|
| Product: | Mesa | Reporter: | David Ronis <David.Ronis> |
| Component: | Drivers/DRI/nouveau | Assignee: | Nouveau Project <nouveau> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | critical | ||
| Priority: | medium | ||
| Version: | git | ||
| Hardware: | x86 (IA32) | ||
| OS: | Linux (All) | ||
| Whiteboard: | |||
| i915 platform: | i915 features: | ||
|
Description
David Ronis
2013-06-03 18:12:21 UTC
I just rebuilt with less aggressive optimization flags. Instead of -march=native -msse2 -mfpmath=sse -O3 -ffast-math -funroll-loops -fomit-frame-pointer -floop-interchange -floop-strip-mine -floop-block I tried -O2 -fomit-frame-pointer It now compiles, so I guess that this is a compiler regression. This problem is still here. Correcting component - nouveau (nvc0) related Cannot seem to reproduce $ export CFLAGS="-march=native -msse2 -mfpmath=sse -O3 -ffast-math -funroll-loops -fomit-frame-pointer -floop-interchange -floop-strip-mine -floop-block" export CXXFLAGS="$CFLAGS" # Build mesa with Gallium3D hardware drivers $ ./autogen.sh --prefix=/usr --with-dri-drivers= --with-state-trackers=dri --disable-egl --with-gallium-drivers=nouveau --disable-gallium-llvm Note added "--with-dri-drivers=" to prevent compilation of intel dri module Can you ensure * you are using ./autogen.sh ... rather than ./configure * the source folder is clean - git clean -fxd Using gcc 4.8.1 $ gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-unknown-linux-gnu/4.8.1/lto-wrapper Target: x86_64-unknown-linux-gnu Configured with: /build/gcc-multilib/src/gcc-4.8.1/configure --prefix=/usr --libdir=/usr/lib --libexecdir=/usr/lib --mandir=/usr/share/man --infodir=/usr/share/info --with-bugurl=https://bugs.archlinux.org/ --enable-languages=c,c++,ada,fortran,go,lto,objc,obj-c++ --enable-shared --enable-threads=posix --with-system-zlib --enable-__cxa_atexit --disable-libunwind-exceptions --enable-clocale=gnu --disable-libstdcxx-pch --enable-gnu-unique-object --enable-linker-build-id --enable-cloog-backend=isl --disable-cloog-version-check --enable-lto --enable-gold --enable-ld=default --enable-plugin --with-plugin-ld=ld.gold --with-linker-hash-style=gnu --disable-install-libiberty --enable-multilib --disable-libssp --disable-werror --enable-checking=release Thread model: posix gcc version 4.8.1 (GCC) Are you using ccache or distcc ? Ideally attach/link your SlackBuild Please provide repro steps. I'm inclined to believe this is a problem in the environment, and not a core gcc bug. But those are some trippy optimization flags, so who knows. Be sure to specify the platform you're building for (given the sse2 flag, x86 or x86_64... but which one... I guess x86 since x86_64 implies sse2). If you can reproduce this by just running a single gcc command (like the one you pasted, but figure out the actual gcc invocation), you should file a gcc bug too. No response to information request in over a month. Closing as invalid. |
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.