public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/114566] [11/12/13/14 Regression] Misaligned vmovaps when compiling with stack-protector-strong for znver4
Date: Thu, 04 Apr 2024 17:14:39 +0000 [thread overview]
Message-ID: <bug-114566-4-pWpBAidejZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-114566-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114566
--- Comment #15 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #14)
> Marking for 14 as well because I believe the trunk commit just made it
> latent there rather than fixed.
You might be able to reproduce it on the trunk with -fno-vect-cost-model
because the patch which made it latent was to the cost model.
next prev parent reply other threads:[~2024-04-04 17:14 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-02 18:19 [Bug c/114566] New: Misaligned vmovaps when compiling libvorbis " yshuiv7 at gmail dot com
2024-04-02 18:28 ` [Bug target/114566] " pinskia at gcc dot gnu.org
2024-04-02 19:33 ` yshuiv7 at gmail dot com
2024-04-02 20:15 ` yshuiv7 at gmail dot com
2024-04-02 20:22 ` yshuiv7 at gmail dot com
2024-04-02 20:28 ` yshuiv7 at gmail dot com
2024-04-02 20:37 ` pinskia at gcc dot gnu.org
2024-04-02 20:40 ` yshuiv7 at gmail dot com
2024-04-02 20:44 ` [Bug target/114566] Misaligned vmovaps when compiling with stack-protector-strong " pinskia at gcc dot gnu.org
2024-04-04 15:22 ` jakub at gcc dot gnu.org
2024-04-04 15:23 ` [Bug target/114566] [11/12/13 Regression] " jakub at gcc dot gnu.org
2024-04-04 15:40 ` jakub at gcc dot gnu.org
2024-04-04 15:46 ` jakub at gcc dot gnu.org
2024-04-04 16:33 ` jakub at gcc dot gnu.org
2024-04-04 16:57 ` jakub at gcc dot gnu.org
2024-04-04 17:08 ` [Bug target/114566] [11/12/13/14 " jakub at gcc dot gnu.org
2024-04-04 17:14 ` pinskia at gcc dot gnu.org [this message]
2024-04-05 10:30 ` [Bug tree-optimization/114566] " jakub at gcc dot gnu.org
2024-04-05 12:56 ` cvs-commit at gcc dot gnu.org
2024-04-05 12:57 ` [Bug tree-optimization/114566] [11/12/13 " jakub at gcc dot gnu.org
2024-04-21 4:08 ` cvs-commit at gcc dot gnu.org
2024-04-23 6:45 ` [Bug tree-optimization/114566] [11/12 " jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-114566-4-pWpBAidejZ@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).