https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
David Edelsohn changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #14 from Thomas Koenig ---
Because the version in bugzilla is set to 10.0, so I assumed it occurred there,
too.
Even better if it is not there.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #13 from David Edelsohn ---
Committed, but why gcc-10? I don't see the testcase on that branch.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #12 from Thomas Koenig ---
(In reply to David Edelsohn from comment #11)
> With the patch the testcase succeeds on both powerpc-ibm-aix7.2.0.0 (big
> endian) and powerpc64-linux (little endian)
OK for master and gcc-10 then (unless y
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #11 from David Edelsohn ---
With the patch the testcase succeeds on both powerpc-ibm-aix7.2.0.0 (big
endian) and powerpc64-linux (little endian)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #10 from David Edelsohn ---
Created attachment 48809
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48809&action=edit
Updated regex for either endianness
The new patch updates the regexps to accept the result for either endiann
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #9 from David Edelsohn ---
This set of regexps works for me:
! { dg-final { scan-tree-dump { \(\*var\.str2\)\[1\]{lb: 1 sz: 4} =
"(d\\x00\\x
00|\\x00\\x00\\x00d)"\[1\]{lb: 1 sz: 4};} "original" } }
! { dg-final { scan-tree-dump { _
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #8 from David Edelsohn ---
It uses . where it wants to consume a quotation mark (").
Because the BE/LE difference is flipping characters, would it negate the
purpose of the test to check for one or zero characters?
! { dg-final { sc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
Thomas Koenig changed:
What|Removed |Added
CC||seurer at linux dot
vnet.ibm.com
--- Co
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #6 from Thomas Koenig ---
Created attachment 48795
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48795&action=edit
Dump file on big-endian system
If anybody wants to do the magic for the patterns on big-endian systems,
here is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #5 from Thomas Koenig ---
Created attachment 48794
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48794&action=edit
patch for the test case, skipping the test on big-endian targets
This implements Segher's suggestion to skip th
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #4 from Segher Boessenkool ---
Or even just { target le } yes. You can put that as the selector on just
the scan tests, and even do a separate BE version as well.
You can quote regexps with {} instead of "", that makes them much m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #3 from David Edelsohn ---
{ target { le } }
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
--- Comment #2 from Thomas Koenig ---
The problem is in the scans; the code runs fine.
Does anybody have the dejagnu-fu to run the scans only on little-endian
systems?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95918
David Edelsohn changed:
What|Removed |Added
Ever confirmed|0 |1
Status|UNCONFIRMED
15 matches
Mail list logo
