https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #11 from Richard Biener ---
See https://gcc.gnu.org/pipermail/gcc-patches/2022-November/607202.html and the
reaction from Honza.(In reply to Jakub Jelinek from comment #10)
> Also, the other PR is about a function being made const la
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #12 from Jakub Jelinek ---
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614071.html
https://gcc.gnu.org/pipermail/gcc-patches/2023-March/614070.html
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #13 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:ed626f18b189920aeed9974aded3f9cb6f25b543
commit r13-6849-ged626f18b189920aeed9974aded3f9cb6f25b543
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
Martin Liška changed:
What|Removed |Added
CC||marxin at gcc dot gnu.org,
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
Richard Biener changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
S
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #3 from Richard Biener ---
OK, it's a late IPA pass doing the clones it seems. The scalar node got the
'const' stripped btw, but the call fntype still has it via the attributes.
It loses 'const' by
Old value = 252968993
New value
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
Richard Biener changed:
What|Removed |Added
CC||hubicka at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #5 from Richard Biener ---
(In reply to Richard Biener from comment #3)
> OK, it's a late IPA pass doing the clones it seems. The scalar node got the
> 'const' stripped btw, but the call fntype still has it via the attributes.
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #6 from Jakub Jelinek ---
Sure, the FUNCTION_TYPE can be shared, so shouldn't be overwritten in place,
but can be copied with TREE_READONLY cleared on the copy.
So, if we for whatever reason need to clear const flag on some functions
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
Richard Biener changed:
What|Removed |Added
Assignee|rguenth at gcc dot gnu.org |unassigned at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #8 from Andrew Pinski ---
I think PR 106433 is the same exact issue.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #9 from Jakub Jelinek ---
(In reply to Andrew Pinski from comment #8)
> I think PR 106433 is the same exact issue.
It is not. The PR106433 patch doesn't fix this, the bug there is late
set_const_flag, while in this case it is an ea
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106912
--- Comment #10 from Jakub Jelinek ---
Also, the other PR is about a function being made const late when it previously
wasn't, while in this case it is being made non-const after it has been const
before.
/* Drop pure/const flags from instrume
14 matches
Mail list logo