https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Andrew Pinski changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Richard Biener changed:
What|Removed |Added
Target Milestone|5.5 |6.5
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Richard Biener changed:
What|Removed |Added
Target Milestone|5.4 |5.5
--- Comment #11 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Ian Lance Taylor changed:
What|Removed |Added
Status|UNCONFIRMED |WAITING
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Richard Biener changed:
What|Removed |Added
Target Milestone|5.3 |5.4
--- Comment #10 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #9 from Ian Lance Taylor ---
I'm not having any luck reproducing this. I built a 32-bit PPC GNU/Linux (on
the GCC compile farm, which is a PPC64 machine, using glibc 2.18). I deleted
the libgo files and rebuilt them with -fstack-pro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Richard Biener changed:
What|Removed |Added
Target Milestone|5.2 |5.3
--- Comment #8 from Richard Biener
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Richard Biener changed:
What|Removed |Added
Priority|P3 |P4
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #7 from Bill Schmidt ---
FYI, PR65787 only changes behavior for powerpc64le, so it's odd that you would
see any differences with or without those changes. The two patched routines
are never called for big endian.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #6 from boger at us dot ibm.com ---
I think you've said the problem only occurs when using -fstack-protector-strong
and when building with glibc-2.21.
Have you tried using gdb to see where the segv actually occurs?
>gdb go
.
>r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #5 from Matthias Klose ---
building trunk libgo with -fstack-protector-strong yields:
$ go version
fatal error: unexpected signal during runtime execution
[signal 0xb code=0x1 addr=0x3]
goroutine 16 [running]:
:0
:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Adam Conrad changed:
What|Removed |Added
CC||adconrad at 0c3 dot net
--- Comment #4 fro
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
boger at us dot ibm.com changed:
What|Removed |Added
CC||boger at us dot ibm.com
--- Com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #2 from Matthias Klose ---
maybe the changes from PR65787 are unrelated.
Building a compiler which has -fstack-protector strong enabled by default. The
crash goes away when I add -fno-stack-protector to AM_CFLAGS in libgo. So it
sho
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |5.2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66368
--- Comment #1 from Matthias Klose ---
correction: reverting the changes from PR65787 only helps for the 5.1.0
release, not the gcc-5-branch.
16 matches
Mail list logo