https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Martin Liška changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #6 from Martin Liška ---
I have a reduced test-case, but thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #5 from David Binderman ---
Problem seems to go away if I set VALGRIND_OPTS
export VALGRIND_OPTS="--expensive-definedness-checks=yes"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #4 from David Binderman ---
Some progress: make -j 1 with languages set to C only, got this:
/home/dcb/gcc/working/./gcc/xgcc -B/home/dcb/gcc/working/./gcc/
-B/home/dcb/gcc/results.279100.valgrind/x86_64-pc-linux-gnu/bin/
-B/home/dcb
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Martin Liška changed:
What|Removed |Added
Status|WAITING |ASSIGNED
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
--- Comment #2 from David Binderman ---
I am not sure which file was affected. make -j 10 was running, so it could
be one of many.
Fortran is probably not the cause. Beyond trying a make -j 1 build without
fortran, which might take 24 hours or m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92832
Martin Liška changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
