https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #34 from Bill Schmidt ---
Martin, thanks! I can confirm that building and testing Go on ppc64le works
again.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
Martin Jambor changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #32 from Martin Jambor ---
Author: jamborm
Date: Tue Jun 13 11:40:24 2017
New Revision: 249154
URL: https://gcc.gnu.org/viewcvs?rev=249154&root=gcc&view=rev
Log:
[PR80803 2/2] Diligent queuing in SRA grp_write prop
2017-06-13 Marti
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
Martin Jambor changed:
What|Removed |Added
CC||su at cs dot ucdavis.edu
--- Comment #31
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #30 from Martin Jambor ---
I have posted the following two patches to fix this issue to the
mailing list. The second one also includes two simple C testcases:
- https://gcc.gnu.org/ml/gcc-patches/2017-06/msg00833.html
- https://
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #29 from Ian Lance Taylor ---
My apologies for not explaining how to find the compilation commands, and I'm
sorry you had to waste time on it. Using "make GOTESTFLAGS=--trace net/check"
will put the commands in net/check-testlog.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #28 from Martin Jambor ---
Created attachment 41518
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41518&action=edit
Possible fix
I'm testing the attached two patches which should fix the issue. If
everything goes well, I will
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #27 from Martin Jambor ---
Created attachment 41517
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41517&action=edit
Hack for revealing compiler command lines
Thanks Ian, the above was definitely helpful but did not allow me to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #26 from Ian Lance Taylor ---
This should let you run the test binary:
cd TARGET/libgo
make GOTESTFLAGS=--keep net/check
cd gotest*/test
LD_LIBRARY_PATH=../../.libs ./a.out -test.short
The test binary is simply a.out in the gotestNN
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #25 from Martin Jambor ---
(In reply to boger from comment #17)
> I run these tests after a build by first editing the
> src/libgo/testsuite/gotest to set keep=true and trace=true. Then I go to my
> bld directory:
>
> cd bld/powerpc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #24 from Bill Schmidt ---
Sadly, no. This continues to be a problem on r248791.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #23 from Bill Schmidt ---
Testing now...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #22 from Martin Jambor ---
So, PR 80898 is now fixed. Can you please check if this is perhaps a
duplicate? It may as well be.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
Martin Jambor changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #20 from Andrew Pinski ---
(In reply to boger from comment #19)
> Is someone building and testing gccgo on x86_64 on a regular basis? If I
> look at the gcc-testresults output for x86_64 I don't see the go or libgo
> test results lik
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #19 from boger at us dot ibm.com ---
Is someone building and testing gccgo on x86_64 on a regular basis? If I look
at the gcc-testresults output for x86_64 I don't see the go or libgo test
results like I do for ppc64le. Maybe it does
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #18 from Ian Lance Taylor ---
Lynn, thanks for the detailed investigation.
Martin, Lynn is saying that these problems started with the SRA patch for PR
78687 committed on 2017-05-02.
It's odd that this problem only shows up on PPC64
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80803
--- Comment #17 from boger at us dot ibm.com ---
Here's more info on the failures and how to reproduce them. Starting with
commit 247497 there are 7 new failures in the libgo testsuite.
There are 4 that fail with a SEGV at runtime: reflect, arch
18 matches
Mail list logo
