https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239
Jeffrey A. Law changed:
What|Removed |Added
CC||law at gcc dot gnu.org
Prior
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239
--- Comment #8 from Dimitry Andric ---
(In reply to Frank Ch. Eigler from comment #7)
> Wonder if this similar but different diagnostic is closely related:
...
> where the c++ code in question is a straight
>
> vector<> foo;
> vector<>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239
--- Comment #7 from Frank Ch. Eigler ---
Wonder if this similar but different diagnostic is closely related:
https://kojipkgs.fedoraproject.org//work/tasks/6259/112176259/build.log
[...]
inlined from ‘mutatee::instrument_dynprobe_target(BP
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239
--- Comment #6 from Andrew Pinski ---
Why the warning only happens with the 2 elements in frame_t, I have no idea
really since there seems not to be any changes in the final IR (except for an
extra load/store for those 2 elements).
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239
--- Comment #5 from Andrew Pinski ---
Note the missed optimization was there in GCC 12, just the diagnostic was not.
We have:
```
_4 = MEM[(const unsigned char * const &)current_frame__2(D) + 24];
_7 = MEM[(const unsigned char * const &)cur
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113239
Richard Biener changed:
What|Removed |Added
Summary|[13 regression] After |[13/14 regression] After
