https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
--- Comment #10 from Ian Lance Taylor ---
Thanks. This may be another example of https://gcc.gnu.org/PR94466.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
--- Comment #9 from Daniel Kolesa ---
it finishes with -fno-var-tracking, though it does take up a few gigs of memory
and takes a while, this is consistent with the default behavior on x86_64 where
it does the same thing.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
Ian Lance Taylor changed:
What|Removed |Added
CC||ian at airs dot com
--- Comment #8 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
Daniel Kolesa changed:
What|Removed |Added
Target||ppc64le-linux-gnu
--- Comment #7 from Da
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
--- Comment #6 from Daniel Kolesa ---
Another thing of note, the gccgo command that hangs is the same on both x86_64
and ppc64le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
Daniel Kolesa changed:
What|Removed |Added
Target|powerpc64le-linux-gnu |
--- Comment #5 from Daniel Kolesa ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
--- Comment #4 from Daniel Kolesa ---
Oh, also, sorry, the process that *actually* gets stuck is go1, not gc1, that
was a typo.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
--- Comment #3 from Daniel Kolesa ---
The steps I took to reproduce the problem:
1) Grab a Go source release
2) Install gccgo including the 'go' command
3) Then do something like:
cd go-1.x
export GOROOT_BOOTSTRAP=/usr/lib/go/9.3.0
export GOROO
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
--- Comment #2 from Daniel Kolesa ---
It reproduces on any GCC 9.x series, and when building *any* version of the
official Go compiler (tested 1.12-1.14), and many other projects (e.g. gitea).
I'm not sure if it reproduces on x86_64, as I don't h
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94611
Richard Biener changed:
What|Removed |Added
CC||iant at google dot com
Compone
10 matches
Mail list logo
