public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dje at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/107018] New: [13 Regression] libgcc unwind-dw2-fde references undeclared variable
Date: Fri, 23 Sep 2022 13:28:11 +0000	[thread overview]
Message-ID: <bug-107018-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 107018
           Summary: [13 Regression] libgcc unwind-dw2-fde references
                    undeclared variable
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: bootstrap
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dje at gcc dot gnu.org
  Target Milestone: ---

in_shutdown is declared within #ifdef ATOMIC_FDE_FAST_PATH but used outside the
scope of that macro.  This causes an undeclared variable that causes libgcc
build to fail and breaks bootstrap.



#ifdef ATOMIC_FDE_FAST_PATH
#include "unwind-dw2-btree.h"

static struct btree registered_frames;
static bool in_shutdown;

static void
release_registered_frames (void) __attribute__ ((destructor (110)));
static void
release_registered_frames (void)
{
  /* Release the b-tree and all frames. Frame releases that happen later are
   * silently ignored */
  btree_destroy (&registered_frames);
  in_shutdown = true;
}

static void
get_pc_range (const struct object *ob, uintptr_type *range);
static void
init_object (struct object *ob);

#else

             reply	other threads:[~2022-09-23 13:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-23 13:28 dje at gcc dot gnu.org [this message]
2022-09-26  7:40 ` [Bug bootstrap/107018] " marxin at gcc dot gnu.org
2022-09-26  7:48 ` marxin 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-107018-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: 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).