public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libgcc/111731] [13/14 regression] gcc_assert is hit at libgcc/unwind-dw2-fde.c#L291
Date: Tue, 02 Apr 2024 08:37:46 +0000	[thread overview]
Message-ID: <bug-111731-4-9xTqywwdiJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111731-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-13 branch has been updated by Thomas Neumann
<tneumann@gcc.gnu.org>:

https://gcc.gnu.org/g:11f37868bb5812c4f0ac023909f5421595f68a43

commit r13-8555-g11f37868bb5812c4f0ac023909f5421595f68a43
Author: Thomas Neumann <tneumann@users.sourceforge.net>
Date:   Mon Mar 11 14:35:20 2024 +0100

    handle unwind tables that are embedded within unwinding code [PR111731]

    Original bug report: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111731

    The unwinding mechanism registers both the code range and the unwind
    table itself within a b-tree lookup structure. That data structure
    assumes that is consists of non-overlappping intervals. This
    becomes a problem if the unwinding table is embedded within the
    code itself, as now the intervals do overlap.

    To fix this problem we now keep the unwind tables in a separate
    b-tree, which prevents the overlap.

    libgcc/ChangeLog:
            PR libgcc/111731
            * unwind-dw2-fde.c: Split unwind ranges if they contain the
            unwind table.

  parent reply	other threads:[~2024-04-02  8:37 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-09  2:17 [Bug libgcc/111731] New: " crazylht at gmail dot com
2023-10-09  2:18 ` [Bug libgcc/111731] " crazylht at gmail dot com
2023-10-09  2:20 ` crazylht at gmail dot com
2023-10-09  9:57 ` rguenth at gcc dot gnu.org
2024-03-11 11:51 ` dimitar.yordanov at sap dot com
2024-03-11 12:03 ` tneumann at users dot sourceforge.net
2024-03-11 12:41 ` dimitar.yordanov at sap dot com
2024-03-11 12:55 ` dimitar.yordanov at sap dot com
2024-03-11 12:58 ` tneumann at users dot sourceforge.net
2024-03-11 12:59 ` dimitar.yordanov at sap dot com
2024-03-11 13:02 ` tneumann at users dot sourceforge.net
2024-03-11 13:39 ` dimitar.yordanov at sap dot com
2024-03-11 13:45 ` tneumann at users dot sourceforge.net
2024-03-11 14:10 ` dimitar.yordanov at sap dot com
2024-03-11 18:00 ` jakub at gcc dot gnu.org
2024-03-11 19:52 ` tneumann at users dot sourceforge.net
2024-03-12  6:27 ` tneumann at users dot sourceforge.net
2024-03-12  6:29 ` liuhongt at gcc dot gnu.org
2024-03-13 17:57 ` dimitar.yordanov at sap dot com
2024-03-14  6:48 ` tneumann at users dot sourceforge.net
2024-03-15  9:14 ` dimitar.yordanov at sap dot com
2024-03-22 14:08 ` cvs-commit at gcc dot gnu.org
2024-04-02  8:37 ` cvs-commit at gcc dot gnu.org [this message]
2024-04-02 11:24 ` rguenth 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-111731-4-9xTqywwdiJ@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).