https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
Andrew Pinski changed:
What|Removed |Added
Target Milestone|12.4|14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #13 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:71b68cc559b5d30d07e6b507df7cc6d008f56aad
commit r14-2299-g71b68cc559b5d30d07e6b507df7cc6d008f56aad
Author: Andrew Pinski
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #12 from CVS Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:2e5c1b123d5bc4b7eca91f1eb2dab88d0bcdfcfa
commit r14-2298-g2e5c1b123d5bc4b7eca91f1eb2dab88d0bcdfcfa
Author: Andrew Pinski
Date: F
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
Andrew Pinski changed:
What|Removed |Added
Attachment #55441|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #10 from Andrew Pinski ---
Created attachment 55442
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55442&action=edit
Patch for the two_value pattern
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #9 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #8)
> (In reply to Andrew Pinski from comment #5)
> > I think there is zero_one_value_p is also accepting signed-boolean:32
> > incorrectly too ...
>
> No, zero_one_v
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #8 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #5)
> I think there is zero_one_value_p is also accepting signed-boolean:32
> incorrectly too ...
No, zero_one_value_p is fine as truth_valued_p only accepts single b
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
Andrew Pinski changed:
What|Removed |Added
Attachment #55440|0 |1
is obsolete|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #6 from Andrew Pinski ---
Created attachment 55440
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55440&action=edit
Fixes the first part
Here is the patch which fixes the first part, I will fix zero_one_p too.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #5 from Andrew Pinski ---
I think there is zero_one_value_p is also accepting signed-boolean:32
incorrectly too ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #4 from Richard Biener ---
BOOLEAN_TYPE means it has two values (else undefined), when the values are 0
and 1 the precision can always be 1 and just TYPE_SIZE can be larger when
required
(fortran bools). With values -1 and 0 and vec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
--- Comment #3 from Andrew Pinski ---
/* Optimize
# x_5 in range [cst1, cst2] where cst2 = cst1 + 1
x_5 ? cstN ? cst4 : cst3
# op is == or != and N is 1 or 2
to r_6 = x_5 + (min (cst3, cst4) - cst1) or
r_6 = (min (cst3, cst4) + cs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110487
Andrew Pinski changed:
What|Removed |Added
Summary|invalid wide Boolean value |[12/13/14 Regression]
13 matches
Mail list logo