public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "woodard at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/102027] [11/12/13/14 Regression] ABI break when using vector type in function arg/return value
Date: Mon, 17 Apr 2023 15:15:42 +0000	[thread overview]
Message-ID: <bug-102027-4-U26HDIAB5j@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102027-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102027

--- Comment #10 from Ben Woodard <woodard at redhat dot com> ---
Currently Libabigail is not able to detect this kind of ABI break. We would be
able to detect this if https://dwarfstd.org/issues/221105.1.html were
implemented. As mentioned in the DWARF issue, this would also other languages
and may even simplify some work that debuggers need to do. Since it is just an
ignorable attribute, can we start supporting it even before it is standardized.

  parent reply	other threads:[~2023-04-17 15:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 18:10 [Bug target/102027] New: " mpolacek at gcc dot gnu.org
2021-08-23 18:10 ` [Bug target/102027] [11/12 Regression] " mpolacek at gcc dot gnu.org
2021-08-23 18:49 ` ubizjak at gmail dot com
2021-08-23 19:12 ` ubizjak at gmail dot com
2021-08-23 19:58 ` pinskia at gcc dot gnu.org
2021-08-23 20:25 ` hjl.tools at gmail dot com
2021-08-24  1:47 ` hjl.tools at gmail dot com
2021-08-24  1:50 ` pinskia at gcc dot gnu.org
2021-08-24  7:12 ` rguenth at gcc dot gnu.org
2021-08-24 13:08 ` hjl.tools at gmail dot com
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2023-04-17 15:15 ` woodard at redhat dot com [this message]
2023-05-29 10:05 ` [Bug target/102027] [11/12/13/14 " 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-102027-4-U26HDIAB5j@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).