public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libgcc/110775] [12/13/14 Regression] abort define causing issues in tsystem.h Date: Wed, 06 Mar 2024 10:18:39 +0000 [thread overview] Message-ID: <bug-110775-4-G8be2ZizgS@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-110775-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110775 --- Comment #3 from Richard Earnshaw <rearnsha at gcc dot gnu.org> --- Perhaps we could use #define abort __builtin_trap ? A quick check seems to suggest this will work ok.
next prev parent reply other threads:[~2024-03-06 10:18 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-07-22 2:22 [Bug libgcc/110775] New: arm-openwrt-linux-uclibcgnueabi bug unlvsur at live dot com 2023-07-22 2:27 ` [Bug libgcc/110775] [12/13/14 Regression] abort define causing issues in tsystem.h pinskia at gcc dot gnu.org 2023-07-22 10:05 ` sebastian.huber@embedded-brains.de 2024-03-06 10:18 ` rearnsha at gcc dot gnu.org [this message] 2024-05-07 13:29 ` [Bug libgcc/110775] [12/13/14/15 " jakub at gcc dot gnu.org 2024-05-07 13:40 ` 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-110775-4-G8be2ZizgS@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).