public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows Date: Fri, 01 Apr 2022 17:59:42 +0000 [thread overview] Message-ID: <bug-54412-4-ICZu1dOIrB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54412-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54412 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jakub at gcc dot gnu.org --- Comment #36 from Jakub Jelinek <jakub at gcc dot gnu.org> --- That patch is certainly unacceptable, not only because it affects non-Windows too, but even on Windows it will unnecessarily pessimize e.g. accesses to data sections or heap that can be aligned. If the Windows ABI doesn't align stack or not as much as gcc assumes, then a fix would ensure only automatic vars on Windows are accessed always using unaligned vector instructions provided dynamic stack realignment is not an option.
next prev parent reply other threads:[~2022-04-01 17:59 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-30 1:10 [Bug target/54412] New: Request for 32-byte stack alignment with -mavx on Windows rcopley at gmail dot com 2013-09-10 10:30 ` [Bug target/54412] " ktietz at gcc dot gnu.org 2013-09-10 17:26 ` rcopley at gmail dot com 2013-09-10 17:49 ` rcopley at gmail dot com 2014-09-03 21:17 ` roland at rschulz dot eu 2014-09-04 22:49 ` rcopley at gmail dot com 2014-09-05 1:42 ` roland at rschulz dot eu 2014-09-05 18:40 ` rcopley at gmail dot com 2014-09-05 18:44 ` rcopley at gmail dot com 2014-09-21 1:08 ` rcopley at gmail dot com 2015-09-22 10:51 ` ktietz at gcc dot gnu.org 2021-08-23 3:12 ` [Bug target/54412] minimal 32-byte stack alignment with -mavx on 64-bit Windows arthur200126 at gmail dot com 2021-08-25 5:38 ` dimula73 at gmail dot com 2021-09-26 7:15 ` mehdi.chinoune at hotmail dot com 2022-04-01 15:01 ` lists at coryfields dot com 2022-04-01 15:38 ` ebotcazou at gcc dot gnu.org 2022-04-01 16:27 ` steve at sk2 dot org 2022-04-01 17:59 ` jakub at gcc dot gnu.org [this message] 2022-04-01 20:25 ` ebotcazou at gcc dot gnu.org 2022-04-01 20:50 ` rcopley at gmail dot com 2022-04-01 21:00 ` ebotcazou at gcc dot gnu.org 2022-04-20 14:41 ` hjl.tools at gmail dot com 2024-01-09 10:15 ` ebotcazou at gcc dot gnu.org 2024-03-26 15:12 ` avraham.adler at gmail dot com 2024-03-27 17:42 ` dimula73 at gmail dot com 2024-03-28 17:30 ` avraham.adler at gmail dot com 2024-03-28 20:26 ` ebotcazou 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-54412-4-ICZu1dOIrB@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).