public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia 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: Sat, 22 Jul 2023 02:27:11 +0000	[thread overview]
Message-ID: <bug-110775-4-pmrNTsEpu7@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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Last reconfirmed|                            |2023-07-22
            Summary|arm-openwrt-linux-uclibcgnu |[12/13/14 Regression] abort
                   |eabi bug                    |define causing issues in
                   |                            |tsystem.h
             Status|UNCONFIRMED                 |NEW
   Target Milestone|---                         |12.4
     Ever confirmed|0                           |1

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This was broken by r12-3220-gcaf81d3b57501b1f .

Though it is interesting that uclibc is causing to use emutls.c here ...

  reply	other threads:[~2023-07-22  2:27 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 ` pinskia at gcc dot gnu.org [this message]
2023-07-22 10:05 ` [Bug libgcc/110775] [12/13/14 Regression] abort define causing issues in tsystem.h sebastian.huber@embedded-brains.de
2024-03-06 10:18 ` rearnsha at gcc dot gnu.org
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-pmrNTsEpu7@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).