https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
--- Comment #6 from Alan Modra ---
Author: amodra
Date: Fri Mar 25 09:10:03 2016
New Revision: 234479
URL: https://gcc.gnu.org/viewcvs?rev=234479=gcc=rev
Log:
[RS6000] PR70052, ICE compiling _Decimal128 test case
gcc/
PR target/70052
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
Alan Modra changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
--- Comment #5 from Michael Meissner ---
The intention of the "j" operand is to provide an alternative that can easily
set the floating point value to 0 via XXLXOR. If decimal64 0.0 is not all 0
bits, then we shouldn't allow that alternative.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
--- Comment #4 from Alan Modra ---
Created attachment 38072
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38072=edit
tentative patch
This hasn't been tested much, apart from verifying that the testcase compiles.
I also find that I don't
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
Alan Modra changed:
What|Removed |Added
CC||amodra at gmail dot com
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
--- Comment #2 from David Edelsohn ---
Missing "j" constraint in pattern to generate 0.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70052
Segher Boessenkool changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
