public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "danglin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/103890] New: Generated baseline symbol file seems to have redundant lines
Date: Sun, 02 Jan 2022 18:22:24 +0000	[thread overview]
Message-ID: <bug-103890-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 103890
           Summary: Generated baseline symbol file seems to have redundant
                    lines
           Product: gcc
           Version: 12.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: danglin at gcc dot gnu.org
  Target Milestone: ---
              Host: hppa*-*-linux*
            Target: hppa*-*-linux*
             Build: hppa*-*-linux*

When I generated a new baseline symbols file, it has lines with and without
symbol versions:

FUNC:_ZGTtNKSt11logic_error4whatEv
FUNC:_ZGTtNKSt11logic_error4whatEv@@GLIBCXX_3.4.22
FUNC:_ZGTtNKSt13bad_exception4whatEv
FUNC:_ZGTtNKSt13bad_exception4whatEv@@CXXABI_1.3.10
FUNC:_ZGTtNKSt13bad_exceptionD1Ev
FUNC:_ZGTtNKSt13bad_exceptionD1Ev@@CXXABI_1.3.10
FUNC:_ZGTtNKSt13runtime_error4whatEv
FUNC:_ZGTtNKSt13runtime_error4whatEv@@GLIBCXX_3.4.22
[...]

None of the other baseline_symbols.txt files duplicate this info.

File does pass abi check though.

             reply	other threads:[~2022-01-02 18:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-02 18:22 danglin at gcc dot gnu.org [this message]
2022-01-02 18:49 ` [Bug libstdc++/103890] " schwab@linux-m68k.org
2022-01-02 19:03 ` dave.anglin at bell dot net
2022-01-04 14:36 ` redi 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-103890-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).