https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #30 from Rich Felker ---
This is a critical codegen issue. Is it really still not fixed in 9.4.0?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Richard Biener changed:
What|Removed |Added
Target Milestone|9.4 |9.5
--- Comment #29 from Richard
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Davin McCall changed:
What|Removed |Added
CC||davmac at davmac dot org
--- Comment #28
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #27 from Luke Dashjr ---
AFAIK it's complete, but I am not a GCC developer.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #26 from Rich Felker ---
Is that complete, or is it unclear whether there are code paths other than
builtin memcmp by which this is hit? Am I correct in assuming that with builtin
memcmp expansion returning NULL_RTX, GCC always
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #25 from Luke Dashjr ---
Created attachment 49334
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49334=edit
Hacky patch to workaround the bug by disabling builtin memcmp always
I wrote and am rebuilding my own systems with a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #24 from Rich Felker ---
The fixes do not seem trivial to backport; lots of conflicts. It would be
really helpful to have versions of the patch that are minified and applicable
to all affected versions that might be shipping in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Martin Sebor changed:
What|Removed |Added
Known to fail|10.1.0 |
--- Comment #23 from Martin Sebor ---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #22 from CVS Commits ---
The releases/gcc-10 branch has been updated by Martin Sebor
:
https://gcc.gnu.org/g:e4c9aac98611f63847ef6c57916808d9a2d7abcb
commit r10-8871-ge4c9aac98611f63847ef6c57916808d9a2d7abcb
Author: Martin Sebor
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #21 from Luke Dashjr ---
Not entirely, I think? At least according to the docs:
if you wish to enable built-in functions selectively when using
-fno-builtin or -ffreestanding, you may define macros such as:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Rich Felker changed:
What|Removed |Added
CC||bugdal at aerifal dot cx
--- Comment #20
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Alexander Monakov changed:
What|Removed |Added
Known to fail||9.3.0
Known to work|9.3.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #18 from Luke Dashjr ---
Someone pointed out to me that the bug metadata says "Known to work: 9.3.0"
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Tim Ruffing changed:
What|Removed |Added
CC||public at timruffing dot de
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
--- Comment #16 from Martin Sebor ---
I think it should be. Let me do it.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Andrew Pinski changed:
What|Removed |Added
CC||blashyrkh at inbox dot ru
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95189
Andrew Pinski changed:
What|Removed |Added
Target Milestone|10.3|9.4
18 matches
Mail list logo
