public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "zfigura at codeweavers dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/110273] i686-w64-mingw32 with -march=znver4 generates AVX instructions without stack alignment Date: Thu, 15 Jun 2023 21:54:07 +0000 [thread overview] Message-ID: <bug-110273-4-eEq7zKOsrS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110273-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110273 --- Comment #1 from Zebediah Figura <zfigura at codeweavers dot com> --- Created attachment 55335 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55335&action=edit gcc -v output, from godbolt
next prev parent reply other threads:[~2023-06-15 21:54 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-06-15 21:53 [Bug target/110273] New: " zfigura at codeweavers dot com 2023-06-15 21:54 ` zfigura at codeweavers dot com [this message] 2023-06-15 22:25 ` [Bug target/110273] " pinskia at gcc dot gnu.org 2023-06-16 8:00 ` amonakov at gcc dot gnu.org 2023-06-16 8:40 ` amonakov at gcc dot gnu.org 2023-06-16 16:50 ` [Bug target/110273] [12/13/14 Regression] i686-w64-mingw32 with -mavx512f " hjl.tools at gmail dot com 2023-06-16 17:24 ` amonakov at gcc dot gnu.org 2023-06-23 9:42 ` rguenth at gcc dot gnu.org 2023-06-26 8:23 ` sjames at gcc dot gnu.org 2023-06-26 8:26 ` amonakov at gcc dot gnu.org 2023-06-26 8:32 ` sjames at gcc dot gnu.org 2023-12-10 17:58 ` hanno@schwalm-bremen.de 2023-12-10 19:59 ` sjames at gcc dot gnu.org 2023-12-10 20:02 ` pinskia at gcc dot gnu.org 2023-12-10 23:28 ` zfigura at codeweavers dot com 2024-01-27 19:01 ` hjl.tools at gmail dot com 2024-03-22 13:45 ` law at gcc dot gnu.org 2024-06-20 9:13 ` [Bug target/110273] [12/13/14/15 " rguenth 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-110273-4-eEq7zKOsrS@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: linkBe 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).