public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "stefan at bytereef dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/98390] AIX: exceptions in threads: IOT/Abort trap(coredump)
Date: Tue, 02 Jan 2024 15:24:28 +0000	[thread overview]
Message-ID: <bug-98390-4-dx8DDiuUvD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98390-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #1 from Stefan Krah <stefan at bytereef dot org> ---

The issue can still be reproduced with a gcc-14 snapshot. ibm-clang++ does not
have this problem. The LLVM unwinder has been reworked for AIX:

https://www.mail-archive.com/cfe-commits@lists.llvm.org/msg275024.html


Would it be possible for gcc to use the LLVM libunwind on AIX? It would be
great if IBM unlocked some funding for this.

gcc often produces faster binaries than clang and this is literally the only
gcc issue on AIX that I've come across after many long running tests. It would
be worth fixing --- both AIX and gcc (except for this issue) are very stable.

      reply	other threads:[~2024-01-02 15:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 10:11 [Bug libgcc/98390] New: " stefan at bytereef dot org
2024-01-02 15:24 ` stefan at bytereef dot org [this message]

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-98390-4-dx8DDiuUvD@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).