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] New: gcc_assert (in_shutdown || ob); build failure for i586-msdosdjgpp target Date: Sat, 24 Sep 2022 17:08:08 +0000 [thread overview] Message-ID: <bug-107026-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107026 Bug ID: 107026 Summary: gcc_assert (in_shutdown || ob); build failure for i586-msdosdjgpp target Product: gcc Version: 13.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: libgcc Assignee: unassigned at gcc dot gnu.org Reporter: unlvsur at live dot com Target Milestone: --- ../../../../../../gcc/libgcc/unwind-dw2-fde.c:287:15: error: 'in_shutdown' undeclared (first use in this function) 287 | gcc_assert (in_shutdown || ob); | ^~~~~~~~~~~ ../../../../../../gcc/libgcc/../gcc/tsystem.h:122:36: note: in definition of macro 'gcc_assert' 122 | #define gcc_assert(EXPR) ((void)(!(EXPR) ? abort (), 0 : 0)) | ^~~~ ../../../../../../gcc/libgcc/unwind-dw2-fde.c:287:15: note: each undeclared identifier is reported only once for each function it appears in 287 | gcc_assert (in_shutdown || ob); | ^~~~~~~~~~~ ../../../../../../gcc/libgcc/../gcc/tsystem.h:122:36: note: in definition of macro 'gcc_assert' 122 | #define gcc_assert(EXPR) ((void)(!(EXPR) ? abort (), 0 : 0)) | ^~~~ make[2]: *** [../../../../../../gcc/libgcc/static-object.mk:17: unwind-dw2-fde.o] Error 1 make[2]: *** Waiting for unfinished jobs....
next reply other threads:[~2022-09-24 17:08 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-09-24 17:08 unlvsur at live dot com [this message] 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 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@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).