https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Richard Biener changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #27 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:ca4a4cc0060cb8ae1a326d6dbfcd9459452e1574
commit r11-10841-gca4a4cc0060cb8ae1a326d6dbfcd9459452e1574
Author: Jakub
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #26 from CVS Commits ---
The releases/gcc-11 branch has been updated by Richard Biener
:
https://gcc.gnu.org/g:bfa476528ceeac96865a48c49f3f1a15d566d209
commit r11-10840-gbfa476528ceeac96865a48c49f3f1a15d566d209
Author: Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Richard Biener changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Jakub Jelinek changed:
What|Removed |Added
Status|ASSIGNED|NEW
Assignee|jakub at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #23 from tt_1 ---
Are there any plans to backport this fix to the gcc-11 branch as well? Seems it
is affected, if you go by the known to fail list.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #22 from Jakub Jelinek ---
Fixed for 12.4, 13.2 and 14.1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #21 from CVS Commits ---
The releases/gcc-12 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:6ef4e2e11c653f1d51f9a304a8d1cf44a53b4ad7
commit r12-9634-g6ef4e2e11c653f1d51f9a304a8d1cf44a53b4ad7
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #20 from CVS Commits ---
The releases/gcc-13 branch has been updated by Jakub Jelinek
:
https://gcc.gnu.org/g:0feece18e6993d02f24a9381ddb5420bb4509554
commit r13-7365-g0feece18e6993d02f24a9381ddb5420bb4509554
Author: Jakub Jelinek
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #19 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:f211757f6fa9515e3fd1a4f66f1a8b48e500c9de
commit r14-1023-gf211757f6fa9515e3fd1a4f66f1a8b48e500c9de
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Jakub Jelinek changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #17 from Sam James ---
Is there by chance a workaround we can apply for this downstream (some flag)?
It prevents building Chromium on arm64 for us w/ gcc unfortunately.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Andrew Pinski changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #15 from rsandifo at gcc dot gnu.org
---
(In reply to Jakub Jelinek from comment #13)
> (In reply to rsand...@gcc.gnu.org from comment #12)
> > (In reply to Andrew Pinski from comment #11)
> > > For bit_and/bit_ior, VECTOR_CST (I
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #14 from rguenther at suse dot de ---
On Mon, 17 Apr 2023, rsandifo at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
>
> --- Comment #10 from rsandifo at gcc dot gnu.org gnu.org> ---
> Might be a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #12 from rsandifo at gcc dot gnu.org
---
(In reply to Andrew Pinski from comment #11)
> For bit_and/bit_ior, VECTOR_CST (I would assume).
Ah, yeah. But then I don't think a top-level POLY_INT_CST_P
cuts it. We'd have the same
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #11 from Andrew Pinski ---
(In reply to rsand...@gcc.gnu.org from comment #10)
> Might be a daft question, but which cases besides
> INTEGER_CST are supposed to be captured by the CONSTANT_CLASS_P?
For bit_and/bit_ior, VECTOR_CST
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #10 from rsandifo at gcc dot gnu.org
---
Might be a daft question, but which cases besides
INTEGER_CST are supposed to be captured by the CONSTANT_CLASS_P?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Richard Biener changed:
What|Removed |Added
CC||rguenth at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
--- Comment #8 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #7)
> Fails even in GCC 11.1.0.
> It is due to match.pd's
>
> /* (x | CST1) & CST2 -> (x & CST2) | (CST1 & CST2) */
> (simplify
> (bit_and (bit_ior @0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109505
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Target Milestone|12.3
22 matches
Mail list logo
