[Bug bootstrap/57125] Build not SMP safe; fails to build bconfig.h

2014-01-03 Thread vcunat at gmail dot com
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57125

Vladimír Čunát  changed:

   What|Removed |Added

 CC||vcunat at gmail dot com

--- Comment #2 from Vladimír Čunát  ---
In this matter I'm quite confused by the intentions of
http://gcc.gnu.org/ml/gcc-patches/2012-07/msg00273.html

It states that host object files depend on CONFIG_H, but these seem to get in
fact built with -DGENERATOR_FILE (according to build log), so through
gentype.c, they include bconfig.h instead of config.h. I don't see that
reflected in build dependencies, and more importantly, I'm not even sure this
consequence was intended/correct.

[Bug bootstrap/60244] GCC-trunk rev.207809, Segmentation fault when executing ".../xgcc -dumpspecs"

2016-03-30 Thread vcunat at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60244

Vladimír Čunát  changed:

   What|Removed |Added

 CC||vcunat at gmail dot com

--- Comment #8 from Vladimír Čunát  ---
I managed to get this problem now with gcc-5.3.0, but I assume some specific
conditions are required to reproduce it. I see no randomness, though: 5/5
segfaults under my conditions on two different machines.

[Bug bootstrap/60244] GCC-trunk rev.207809, Segmentation fault when executing ".../xgcc -dumpspecs"

2016-04-01 Thread vcunat at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60244

--- Comment #9 from Vladimír Čunát  ---
More information about my case: it's x86_64, Linux, gcc-5.3.0 from tarball
being built by gcc-4.8.3. I re-tried with --enable-debug and ran the
segfaulting command in gdb (I filtered seemingly uninteresting lines):

$ gdb -- /tmp/nix-build-gcc-5.3.0.drv-1/build/./gcc/xgcc
(gdb) run -B/tmp/nix-build-gcc-5.3.0.drv-1/build/./gcc/ -dumpspecs
Program received signal SIGSEGV, Segmentation fault.
(gdb) bt full
#0  0x0047ea8c in atexit ()
No symbol table info available.
#1  0x0040fd9a in driver::global_initializations (this=0x7fffd9f0)
at ../../gcc-5.3.0/gcc/gcc.c:6985
No locals.
#2  0x0040fb81 in driver::main (this=0x7fffd9f0, argc=3,
argv=0x7fffdaf8) at ../../gcc-5.3.0/gcc/gcc.c:6900
early_exit = false
#3  0x00416958 in main (argc=3, argv=0x7fffdaf8) at
../../gcc-5.3.0/gcc/gcc-main.c:45
d = {explicit_link_files = 0x47ea00 <__libc_csu_init>
"AWA\211\377AVI\211\366AUI\211\325ATL\215%0\033&", decoded_options = 0x6e6d70, 
  decoded_options_count = 3}

It really puzzles me that the segfault occurs *during* a call to atexit. It
uses glibc-2.23. Any idea about what could be wrong? Thanks.

[Bug bootstrap/60244] GCC-trunk rev.207809, Segmentation fault when executing ".../xgcc -dumpspecs"

2016-04-01 Thread vcunat at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60244

--- Comment #10 from Vladimír Čunát  ---
Now I see the segfault does not happen if I use binutils-2.23 instead of 2.26.
Perhaps the cause is in there then.

[Bug bootstrap/60244] GCC-trunk rev.207809, Segmentation fault when executing ".../xgcc -dumpspecs"

2016-04-05 Thread vcunat at gmail dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60244

--- Comment #11 from Vladimír Čunát  ---
OK, I'm abandoning this problem, regardless of which package actually causes
the problem. I can't see how to progress and I've got some workarounds for my
case: either downgrading to binutils-2.25.1 or upgrading the whole toolchain
(including gcc).