https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92564
--- Comment #3 from boger at gcc dot gnu.org ---
Yes, I tried the value of 0x8 and the test passed. In the issue Ian
mentioned that 0x10 was the default on x86. If we want the same default on
x86 and ppc64 then 0x10 would work since
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92564
boger at gcc dot gnu.org changed:
What|Removed |Added
CC||amodra at gcc dot gnu.org
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: boger at gcc dot gnu.org
CC: cmang at google dot com, seurer at us dot ibm.com
Target Milestone: ---
Timeouts occur in the libgo syscall test when running the
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: boger at gcc dot gnu.org
CC: cmang at google dot com, seurer at us dot ibm.com
Target Milestone: ---
When running the runtime test on ppc64le from trunk, a SIGSEV results. This
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89227
--- Comment #6 from boger at gcc dot gnu.org ---
Works now, thanks.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89227
--- Comment #3 from boger at gcc dot gnu.org ---
(In reply to Ian Lance Taylor from comment #1)
> Same as https://golang.org/issue/29046?
Yes same as the issue. Since we weren't sure if this was a FE or BE bug I
decided to open a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89227
boger at gcc dot gnu.org changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
us: UNCONFIRMED
Severity: normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: boger at gcc dot gnu.org
CC: cmang at google dot com, wschmidt at gcc dot gnu.org
Target Milestone: ---
Target: ppc64l
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=89199
boger at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P2
Severity|normal
Priority: P3
Component: go
Assignee: ian at airs dot com
Reporter: boger at gcc dot gnu.org
CC: cmang at google dot com, wschmidt at gcc dot gnu.org
Target Milestone: ---
Some new intermittent testcase failures started appearing in gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88011
--- Comment #4 from boger at gcc dot gnu.org ---
Created attachment 45005
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45005&action=edit
Hack workaround to show bad loop
Through my debugging I found that if I add the print state
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88011
--- Comment #3 from boger at gcc dot gnu.org ---
Created attachment 45003
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=45003&action=edit
Reproducer testcase for gccgo testresults failures in GCD
You should be able to build thi
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88011
--- Comment #2 from boger at gcc dot gnu.org ---
(In reply to Richard Biener from comment #1)
> C testcase anyone? ;) I never succeeded extracting anything meaningful from
> the Go testsuite logs to be able to reproduce sth (no cut
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870
--- Comment #33 from boger at gcc dot gnu.org ---
Author: boger
Date: Wed Oct 28 16:00:46 2015
New Revision: 229493
URL: https://gcc.gnu.org/viewcvs?rev=229493&root=gcc&view=rev
Log:
Backport of r229009
PR66870 PowerPC64 Enable gold lin
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870
--- Comment #31 from boger at gcc dot gnu.org ---
Author: boger
Date: Thu Oct 8 19:21:45 2015
New Revision: 228623
URL: https://gcc.gnu.org/viewcvs?rev=228623&root=gcc&view=rev
Log:
Backport of rev 228311
PR targ
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66870
--- Comment #20 from boger at gcc dot gnu.org ---
Author: boger
Date: Wed Aug 5 18:07:16 2015
New Revision: 226643
URL: https://gcc.gnu.org/viewcvs?rev=226643&root=gcc&view=rev
Log:
2015-08-15 Lynn Boger
PR target/66870
16 matches
Mail list logo
