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/91710] [9/10/11 Regression] unexpected ABI change note since r9-5650 Date: Thu, 18 Mar 2021 15:52:02 +0000 [thread overview] Message-ID: <bug-91710-4-J1Nl2CwfrJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-91710-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91710 --- Comment #7 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 50421 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50421&action=edit gcc11-pr91710.patch So perhaps pass the old alignment to the caller and let that function verify if it is really a potential ABI change or not?
next prev parent reply other threads:[~2021-03-18 15:52 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-91710-4@http.gcc.gnu.org/bugzilla/> 2020-03-12 11:58 ` [Bug target/91710] [9/10 " jakub at gcc dot gnu.org 2021-03-18 15:52 ` jakub at gcc dot gnu.org [this message] 2021-04-16 18:50 ` [Bug target/91710] [9/10/11 " cvs-commit at gcc dot gnu.org 2021-04-16 18:51 ` [Bug target/91710] [9/10 " jakub at gcc dot gnu.org 2021-06-01 8:15 ` rguenth at gcc dot gnu.org 2022-05-27 9:41 ` [Bug target/91710] [10 " rguenth at gcc dot gnu.org 2022-06-28 10:38 ` jakub at gcc dot gnu.org 2023-07-07 8:35 ` 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-91710-4-J1Nl2CwfrJ@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).