public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug c++/71644] gcc 6.1 generates movaps for unaligned memory
[not found] <bug-71644-4@http.gcc.gnu.org/bugzilla/>
@ 2023-06-14 3:45 ` rr7crecb3z at liamekaens dot com
2023-06-14 3:55 ` pinskia at gcc dot gnu.org
2023-10-09 17:51 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: rr7crecb3z at liamekaens dot com @ 2023-06-14 3:45 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71644
rr7crecb3z at liamekaens dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |rr7crecb3z at liamekaens dot com
--- Comment #1 from rr7crecb3z at liamekaens dot com ---
7 years and this bug is STILL "UNCONFIRMED". I'm here because I ran into this
bug after building Python, using GCC 11.3.0.
The reproduction program provided by justus@gmx.li back in 2016 STILL
reproduces the bug in GCC 11.3.0.
Can't there just be a way to disable the use of the MOVAPS instruction
entirely, without having to disable optimizations that don't have bugs? I'm
sick and tired of dealing with this bug. GCC obviously will never be able to be
trusted to use the MOVAPS instruction correctly.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/71644] gcc 6.1 generates movaps for unaligned memory
[not found] <bug-71644-4@http.gcc.gnu.org/bugzilla/>
2023-06-14 3:45 ` [Bug c++/71644] gcc 6.1 generates movaps for unaligned memory rr7crecb3z at liamekaens dot com
@ 2023-06-14 3:55 ` pinskia at gcc dot gnu.org
2023-10-09 17:51 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-06-14 3:55 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71644
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Last reconfirmed| |2023-06-14
Ever confirmed|0 |1
Status|UNCONFIRMED |NEW
--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Confirmed. PR 83780 has a related issue going on.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug c++/71644] gcc 6.1 generates movaps for unaligned memory
[not found] <bug-71644-4@http.gcc.gnu.org/bugzilla/>
2023-06-14 3:45 ` [Bug c++/71644] gcc 6.1 generates movaps for unaligned memory rr7crecb3z at liamekaens dot com
2023-06-14 3:55 ` pinskia at gcc dot gnu.org
@ 2023-10-09 17:51 ` pinskia at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: pinskia at gcc dot gnu.org @ 2023-10-09 17:51 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71644
Andrew Pinski <pinskia at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cuzdav at gmail dot com
--- Comment #3 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
*** Bug 111742 has been marked as a duplicate of this bug. ***
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2023-10-09 17:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-71644-4@http.gcc.gnu.org/bugzilla/>
2023-06-14 3:45 ` [Bug c++/71644] gcc 6.1 generates movaps for unaligned memory rr7crecb3z at liamekaens dot com
2023-06-14 3:55 ` pinskia at gcc dot gnu.org
2023-10-09 17:51 ` pinskia at gcc dot gnu.org
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).