[Bug c++/61262] New: GCC segfaults
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262 Bug ID: 61262 Summary: GCC segfaults Product: gcc Version: 4.9.0 Status: UNCONFIRMED Severity: critical Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lailavrazda1979 at gmail dot com Since I code, I know that this is gonna be a pretty bad bug report. But I know next to nothing about the code I'm compiling, however, what I do know is, GCC 4.8.x works, while GCC 4.9.0 segfaults. Since I don't know the code, I'll provide complete steps to reproduce it: Clone https://github.com/monero-project/bitmonero.git Enter the new directory (bitmonero) Run: make build-debug VERBOSE=1 Using the debug target is important; there seems to be other issue with building when the release target is used, and that will cause the build to terminate before the segfault. I get the following when building it with one thread: http://pastebin.com/EA3ydhHJ
[Bug c++/61262] GCC segfaults
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61262 --- Comment #1 from lailavrazda1979 at gmail dot com --- A bug that causes GCC to segfault AND is a regression is only normal in severity? I thought a crash is one of those things that should never, EVER happen?
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 lailavrazda1979 at gmail dot com changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #18 from lailavrazda1979 at gmail dot com --- Patch is checked in, so I'm closing this.
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 --- Comment #16 from lailavrazda1979 at gmail dot com --- Okay, no worries.
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 --- Comment #14 from lailavrazda1979 at gmail dot com --- Why wait? I'm not hugely opposed, but bugfixes are bugfixes, and one more fixed bug makes a better 4.9 release, right?
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 --- Comment #12 from lailavrazda1979 at gmail dot com --- Bug still a problem with latest trunk.
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 --- Comment #11 from lailavrazda1979 at gmail dot com --- I don't mean to be a bother, but this hasn't been updated in a while. Has it been fixed?
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 --- Comment #10 from lailavrazda1979 at gmail dot com --- Is this going to be fixed?
[Bug c++/57926] New: Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 Bug ID: 57926 Summary: Atomic functions broken with C++ but not C? Product: gcc Version: unknown Status: UNCONFIRMED Severity: major Priority: P3 Component: c++ Assignee: unassigned at gcc dot gnu.org Reporter: lailavrazda1979 at gmail dot com Note that this possible bug does not trigger with GCC, only G++. Try compiling the code in the attachment with g++. It'll give strange errors, including complaining that an argument must be a non-void pointer when it IS in fact, a non-void pointer.
[Bug c++/57926] Atomic functions broken with C++ but not C?
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57926 --- Comment #1 from lailavrazda1979 at gmail dot com --- Created attachment 30523 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=30523action=edit Code triggering the bug
[Bug c/57928] New: Doesn't compile with ISL 0.12
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57928 Bug ID: 57928 Summary: Doesn't compile with ISL 0.12 Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: lailavrazda1979 at gmail dot com You guys consider checking for 0.10 and up instead of adding an explicit check for every new release?
[Bug c/57630] Error should include -std=c11 and friends
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57630 --- Comment #3 from lailavrazda1979 at gmail dot com --- Looks good to me.
[Bug c/57630] New: Error should include -std=c11 and friends
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57630 Bug ID: 57630 Summary: Error should include -std=c11 and friends Product: gcc Version: 4.8.1 Status: UNCONFIRMED Severity: minor Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: lailavrazda1979 at gmail dot com The following message: error: 'for' loop initial declarations are only allowed in C99 mode minigen.c:88:2: note: use option -std=c99 or -std=gnu99 to compile your code should include -std=c11 and friends.
[Bug other/56057] libbacktrace STILL doesn't honor --disable-werror
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56057 lailavrazda1979 at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||FIXED --- Comment #1 from lailavrazda1979 at gmail dot com 2013-01-24 16:14:29 UTC --- Seems to be fixed now.
[Bug other/56057] New: libbacktrace STILL doesn't honor --disable-werror
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56057 Bug #: 56057 Summary: libbacktrace STILL doesn't honor --disable-werror Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassig...@gcc.gnu.org ReportedBy: lailavrazda1...@gmail.com libbacktrace is not honoring --disable-werror and using -fPIC, causing a warning (which is promoted to an error) when building a native compiler for x86_64-w64-mingw32. This happens with revision 195330, the latest, as of this writing. Errors below: libtool: compile: x86_64-w64-mingw32-gcc -L/root/win64-build/native/x86_64-w64-mingw32/lib -L/root/win64-build/native/mingw/lib -isystem /root/win64-build/native/x86_64-w64-mingw32/include -isystem /root/win64-build/native/mingw/include -DHAVE_CONFIG_H -I. -I../../../gcc-4.8.0/libbacktrace -I ../../../gcc-4.8.0/libbacktrace/../include -I ../../../gcc-4.8.0/libbacktrace/../libgcc -I ../libgcc -funwind-tables -frandom-seed=dwarf.lo -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -Wmissing-format-attribute -Wcast-qual -Werror -fPIC -g -O2 -c ../../../gcc-4.8.0/libbacktrace/dwarf.c -o dwarf.o ../../../gcc-4.8.0/libbacktrace/dwarf.c:1:0: error: -fPIC ignored for target (all code is position independent) [-Werror] /* dwarf.c -- Get file/line information from DWARF for backtraces. ^ cc1: all warnings being treated as errors make[3]: *** [dwarf.lo] Error 1 make[3]: Leaving directory `/root/win64-build/src/gcc-build/x86_64-w64-mingw32/libbacktrace' make[2]: *** [all] Error 2 make[2]: Leaving directory `/root/win64-build/src/gcc-build/x86_64-w64-mingw32/libbacktrace' make[1]: *** [all-target-libbacktrace] Error 2 make[1]: Leaving directory `/root/win64-build/src/gcc-build' make: *** [all] Error 2
[Bug c/55819] Conflicting declaration of getcwd breaks mingw-w64 compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55819 lailavrazda1979 at gmail dot com changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution||WORKSFORME --- Comment #3 from lailavrazda1979 at gmail dot com 2013-01-21 05:28:14 UTC --- Seems to work now, strangely. Must have been an issue with my setup.
[Bug other/56042] Many errors building GCC trunk with mingw-w64 rev. 5542
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56042 --- Comment #2 from lailavrazda1979 at gmail dot com 2013-01-20 02:13:29 UTC --- Strange, it seems to work with the last release of mingw-w64. I configured the headers with: ./configure --build=$CROSS_HOST --host=$CROSS_TGT --prefix=$CROSS_DIR
[Bug other/56042] New: Many errors building GCC trunk with mingw-w64 rev. 5542
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56042 Bug #: 56042 Summary: Many errors building GCC trunk with mingw-w64 rev. 5542 Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: normal Priority: P3 Component: other AssignedTo: unassig...@gcc.gnu.org ReportedBy: lailavrazda1...@gmail.com Created attachment 29216 -- http://gcc.gnu.org/bugzilla/attachment.cgi?id=29216 Error log When building GCC with the following configure line, I get a massive amount of errors relating to the headers. ../gcc-4.8.0/configure --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=x86_64-w64-mingw32 --prefix=$CROSS_DIR --libexecdir=$CROSS_DIR/lib --enable-clocale=gnu --enable-__cxa_atexit --enable-languages=c,c++ --enable-targets=all --enable-checking=release --disable-shared --disable-nls --disable-werror --disable-isl-version-check --with-system-zlib --with-host-libstdcxx=-lstdc++ -lsupc++ --with-local-prefix=$CROSS_DIR --with-sysroot=$CROSS_DIR --with-isl=$CROSS_DIR --with-cloog=$CROSS_DIR The errors are attached.
[Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925 --- Comment #4 from lailavrazda1979 at gmail dot com 2013-01-14 21:26:36 UTC --- I tried building several compilers (4.7.2), none of which understand the '-mfxsr' option. One was configured with: ../gcc-4.7.2/configure --build=x86_64-unknown-linux-gnu --host=x86_64-unknown-linux-gnu --target=x86_64-w64-mingw32 --prefix=$CROSS_DIR --libexecdir=$CROSS_DIR/lib --enable-clocale=gnu --enable-__cxa_atexit --enable-languages=c,c++ --enable-targets=all --enable-cloog-backend=ppl --disable-shared --disable-nls --disable-werror --with-host-libstdcxx=-lstdc++ -lsupc++ --with-local-prefix=$CROSS_DIR --with-sysroot=$CROSS_DIR --with-ppl=$CROSS_DIR --with-cloog=$CROSS_DIR make all-gcc make install-gcc After that, I build the mingw-w64 library, went back to my GCC build dir, and did: make make install
[Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925 --- Comment #6 from lailavrazda1979 at gmail dot com 2013-01-14 23:18:30 UTC --- So, you need GCC 4.8 to build GCC 4.8? That's just... why? Doesn't that mean it's basically impossible to build GCC 4.8 without a binary of it first?
[Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925 lailavrazda1979 at gmail dot com changed: What|Removed |Added Status|RESOLVED|UNCONFIRMED Resolution|INVALID | --- Comment #8 from lailavrazda1979 at gmail dot com 2013-01-14 23:43:54 UTC --- Oh, okay. That makes sense. Thank you.
[Bug other/55925] Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925 --- Comment #2 from lailavrazda1979 at gmail dot com 2013-01-13 23:31:01 UTC --- How did I configure which GCC? The cross compiler or the native one?
[Bug other/55925] New: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55925 Bug #: 55925 Summary: Unrecognized command line option '-mfxsr' when building x86_64-w64-mingw32 native compiler Classification: Unclassified Product: gcc Version: 4.8.0 Status: UNCONFIRMED Severity: major Priority: P3 Component: other AssignedTo: unassig...@gcc.gnu.org ReportedBy: lailavrazda1...@gmail.com When building a native x86_64-w64-mingw32 compiler using a 4.7.2 cross compiler, I get the following: x86_64-w64-mingw32-gcc -L/root/win64-build/native/x86_64-w64-mingw32/lib -L/root/win64-build/native/mingw/lib -isystem /root/win64-build/native/x86_64-w64-mingw32/include -isystem /root/win64-build/native/mingw/include-g -O2 -O2 -g -O2 -DIN_GCC -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wstrict-prototypes -Wmissing-prototypes -Wold-style-definition -isystem ./include -g -DIN_LIBGCC2 -fbuilding-libgcc -fno-stack-protector -I. -I. -I../.././gcc -I../../../gcc-4.8.0/libgcc -I../../../gcc-4.8.0/libgcc/. -I../../../gcc-4.8.0/libgcc/../gcc -I../../../gcc-4.8.0/libgcc/../include -I../../../gcc-4.8.0/libgcc/config/libbid -DENABLE_DECIMAL_BID_FORMAT -DHAVE_CC_TLS -DUSE_EMUTLS -o crtfastmath.o -MT crtfastmath.o -MD -MP -MF crtfastmath.dep -mfxsr -msse -c ../../../gcc-4.8.0/libgcc/config/i386/crtfastmath.c x86_64-w64-mingw32-gcc: error: unrecognized command line option '-mfxsr' make[2]: *** [crtfastmath.o] Error 1 make[2]: Leaving directory `/root/win64-build/src/gcc-build/x86_64-w64-mingw32/libgcc' make[1]: *** [all-target-libgcc] Error 2 make[1]: Leaving directory `/root/win64-build/src/gcc-build' make: *** [all] Error 2 I can't find any documentation at all on this '-mfxsr' option. What is it, and why is it being used here?
[Bug c/55819] Conflicting declaration of getcwd breaks mingw-w64 compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55819 --- Comment #2 from lailavrazda1979 at gmail dot com 2012-12-31 19:42:19 UTC --- I know it works with 4.7.2, and I think 4.7.3 as well.
[Bug c/55819] New: Conflicting declaration of getcwd breaks mingw-w64 compile
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55819 Bug #: 55819 Summary: Conflicting declaration of getcwd breaks mingw-w64 compile Classification: Unclassified Product: gcc Version: unknown Status: UNCONFIRMED Severity: major Priority: P3 Component: c AssignedTo: unassig...@gcc.gnu.org ReportedBy: lailavrazda1...@gmail.com Output when compiling on x86_64-unknown-linux-gnu for x86_64-w64-mingw32: x86_64-w64-mingw32-g++ -c -DIN_GCC_FRONTEND -g -O2 -DIN_GCC -fno-exceptions -fno-rtti -fasynchronous-unwind-tables -W -Wall -Wno-narrowing -Wwrite-strings -Wcast-qual -Wmissing-format-attribute -pedantic -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings -DHAVE_CONFIG_H -I. -Ic -I../../gcc-4.8.0/gcc -I../../gcc-4.8.0/gcc/c -I../../gcc-4.8.0/gcc/../include -I../../gcc-4.8.0/gcc/../libcpp/include -I/root/win64-build/native/include -I/root/win64-build/native/include -I/root/win64-build/native/include -I../../gcc-4.8.0/gcc/../libdecnumber -I../../gcc-4.8.0/gcc/../libdecnumber/bid -I../libdecnumber -I../../gcc-4.8.0/gcc/../libbacktrace -DCLOOG_INT_GMP -I/root/win64-build/native/include ../../gcc-4.8.0/gcc/c/c-lang.c -o c/c-lang.o In file included from ../../gcc-4.8.0/gcc/c/c-lang.c:24:0: ../../gcc-4.8.0/gcc/system.h:426:36: error: declaration of C function 'char* getcwd(char*, size_t)' conflicts with In file included from /usr/lib/gcc/x86_64-w64-mingw32/4.7.2/../../../../x86_64-w64-mingw32/include/unistd.h:10:0, from ../../gcc-4.8.0/gcc/system.h:256, from ../../gcc-4.8.0/gcc/c/c-lang.c:24: /usr/lib/gcc/x86_64-w64-mingw32/4.7.2/../../../../x86_64-w64-mingw32/include/io.h:266:17: error: previous declaration 'char* getcwd(char*, int)' here make[1]: *** [c/c-lang.o] Error 1 make[1]: Leaving directory `/root/win64-build/src/gcc-build/gcc' make: *** [all-gcc] Error 2
