https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill changed:
What|Removed |Added
Attachment #56792|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill changed:
What|Removed |Added
Attachment #56698|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #14 from Robin Dapp ---
Yes, that's the culprit. I already pushed a fix yesterday.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #12 from Robin Dapp ---
Ok, on my server the difference is that I didn't add vext_spec=v1.0 to the qemu
options. This caused the qemu diagnostic which would of course not match the
expected output.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #11 from Robin Dapp ---
Verified they work locally but also fail on a different server. Also fail
without vector and at -O0. Maybe it's different tcl versions or the shell
doing wonky stuff?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #10 from Robin Dapp ---
I didn't yet look at all those closer because they are more dump failures than
real execution failures.
The ones I checked are
expected
"^foobar$" but got:
"foobar"
so I considered this rather an environmen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #9 from JuzheZhong ---
=== gfortran: Unexpected fails for rv64gcv lp64d medany ===
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O0 output pattern test
FAIL: gfortran.dg/dollar_edit_descriptor_3.f -O1 output pa
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill changed:
What|Removed |Added
Attachment #56659|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
Patrick O'Neill changed:
What|Removed |Added
Attachment #56615|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #5 from Patrick O'Neill ---
I built all the zvl variants as a multilib. It seems like that caused them to
interfere with eachother (potentially picking up the wrong glibc?). I'll rerun
with separate runs & update the issues with upda
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #4 from Patrick O'Neill ---
Investigating this now. I'll let you know what I find out.
All these tests were run in the same environment so be wary when looking at any
of them until I figure out the environment issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #3 from Robin Dapp ---
I cannot reproduce this either. Just started with binop/* and don't see any
fails locally. Patrick, could you check what caused this?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
JuzheZhong changed:
What|Removed |Added
CC||juzhe.zhong at rivai dot ai
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
--- Comment #1 from Patrick O'Neill ---
Related issues:
128: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112583
256: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112597
512: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112598
1024: https://gcc.
16 matches
Mail list logo