public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "unlvsur at live dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/107026] [13 Regression] gcc_assert (in_shutdown || ob); build failure for i586-msdosdjgpp target
Date: Sun, 25 Sep 2022 06:06:15 +0000 [thread overview]
Message-ID: <bug-107026-4-gyATaP2dmD@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107026-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107026
--- Comment #3 from cqwrteur <unlvsur at live dot com> ---
(In reply to Andrew Pinski from comment #2)
> Introduced by r13-2801-g94ccaf62c378c3.
>
>
> The use in_shutdown is not inside the #ifdef ATOMIC_FDE_FAST_PATH
> case.
this also happens with x86_64-w64-mingw32 target
btw it is weird why --disable-sjlj-exceptions is not working any more for
x86_64-w64-mingw32 target
next prev parent reply other threads:[~2022-09-25 6:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-24 17:08 [Bug libgcc/107026] New: " unlvsur at live dot com
2022-09-24 17:09 ` [Bug libgcc/107026] " unlvsur at live dot com
2022-09-24 19:07 ` [Bug libgcc/107026] [13 Regression] " pinskia at gcc dot gnu.org
2022-09-25 6:06 ` unlvsur at live dot com [this message]
2022-09-25 23:21 ` tnfchris at gcc dot gnu.org
2022-09-25 23:23 ` tnfchris at gcc dot gnu.org
2022-09-26 5:44 ` tneumann at users dot sourceforge.net
2022-09-26 7:48 ` marxin at gcc dot gnu.org
2022-09-26 13:57 ` tschwinge at gcc dot gnu.org
2022-09-26 14:00 ` tneumann at users dot sourceforge.net
2022-09-27 9:17 ` tschwinge 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-107026-4-gyATaP2dmD@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).