https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #22 from Jonathan Wakely ---
(In reply to Jakub Jelinek from comment #19)
> I've posted
> https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598896.html
> patch for this, waiting for Jon's review.
N.B. that was committed as
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Richard Biener changed:
What|Removed |Added
Priority|P3 |P2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Richard Biener changed:
What|Removed |Added
Target Milestone|12.2|12.3
--- Comment #21 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #20 from Richard Biener ---
See also https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598839.html
and https://gcc.gnu.org/pipermail/gcc-patches/2022-July/598840.html
which I didn't pursue further since they didn't seem to catch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #19 from Jakub Jelinek ---
(In reply to Jason Merrill from comment #17)
> Created attachment 53474 [details]
> patch to work around the issue in the library
I've posted
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #18 from Jason Merrill ---
(In reply to Jason Merrill from comment #17)
> There's probably a way to help the optimizer out without the
> __builtin_unreachable hammer, as for 98465; suggestions are welcome.
..like
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Jonathan Wakely changed:
What|Removed |Added
CC||hi at jdoubleu dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #15 from Richard Biener ---
Note on trunk we get things way less optimized and end up with
[local count: 695302893]:
__x.38_144 = (long unsigned int) " ";
__y.39_145 = (long unsigned int) _137;
if (__x.38_144 < __y.39_145)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #14 from rguenther at suse dot de ---
On Tue, 26 Jul 2022, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
>
> --- Comment #12 from Jakub Jelinek ---
> My preference would be still to make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #13 from Jonathan Wakely ---
I think the vast majority of string mutations involve
inserting/appending/substituting an unrelated string, so non-overlapping. We
can make your change on trunk.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
--- Comment #12 from Jakub Jelinek ---
My preference would be still to make the overlap case out-of-line as mentioned
in PR105329, but I don't have statistics on whether the overlap case is really
cold in real-world. If yes, it would make
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Jonathan Wakely changed:
What|Removed |Added
CC|jwakely at redhat dot com |redi at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Andrew Pinski changed:
What|Removed |Added
CC||me+gccbugzilla at s5 dot pm
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105651
Martin Liška changed:
What|Removed |Added
Keywords|needs-bisection,|
|needs-reduction
16 matches
Mail list logo
