public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug libc/31767] New: Libgcc symbols should be compat symbols
Date: Mon, 20 May 2024 23:03:07 +0000	[thread overview]
Message-ID: <bug-31767-131@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31767

            Bug ID: 31767
           Summary: Libgcc symbols should be compat symbols
           Product: glibc
           Version: 2.40
            Status: NEW
          Severity: normal
          Priority: P2
         Component: libc
          Assignee: unassigned at sourceware dot org
          Reporter: hjl.tools at gmail dot com
                CC: drepper.fsp at gmail dot com
  Target Milestone: ---

i386 libc.so has:

   128: 001ab760   305 FUNC    GLOBAL DEFAULT   15
__deregister_frame_info_bases@@GCC_3.0
   645: 001ab410   110 FUNC    GLOBAL DEFAULT   15
__register_frame_info_bases@@GCC_3.0
   774: 001ab630   182 FUNC    GLOBAL DEFAULT   15
__register_frame_info_table@@GLIBC_2.0
  1209: 001ab480    82 FUNC    GLOBAL DEFAULT   15
__register_frame_info@@GLIBC_2.0
  1817: 001ab570   182 FUNC    GLOBAL DEFAULT   15
__register_frame_info_table_bases@@GCC_3.0
  1932: 001ab4e0   130 FUNC    GLOBAL DEFAULT   15 __register_frame@@GLIBC_2.0
  2367: 001ab8a0    47 FUNC    GLOBAL DEFAULT   15
__deregister_frame_info@@GLIBC_2.0
  2510: 001ab8d0    87 FUNC    GLOBAL DEFAULT   15
__deregister_frame@@GLIBC_2.0
  3033: 001ab6f0   103 FUNC    GLOBAL DEFAULT   15
__register_frame_table@@GLIBC_2.0
  2548: 001abb70   201 FUNC    GLOBAL DEFAULT   15 _Unwind_Find_FDE@@GCC_3.0

Should they be compat symbols?

-- 
You are receiving this mail because:
You are on the CC list for the bug.

                 reply	other threads:[~2024-05-20 23:03 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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-31767-131@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@sourceware.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).