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 middle-end/113182] [14 Regression] FAIL: g++.dg/cpp0x/udlit-namespace.C  -std=c++14 execution test
Date: Fri, 12 Jan 2024 12:59:05 +0000	[thread overview]
Message-ID: <bug-113182-4-c9xR68ubcU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-113182-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #21 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jakub Jelinek <jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:c05beab4ae240a593299c08ef8c775d91187a141

commit r14-7188-gc05beab4ae240a593299c08ef8c775d91187a141
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Jan 12 13:58:07 2024 +0100

    varasm: Fix up process_pending_assemble_externals [PR113182]

    John reported that on HP-UX we no longer emit needed external libcalls.

    The problem is that we didn't strip name encoding when looking up
    the identifiers in assemble_external_libcall and
    process_pending_assemble_externals, while
    assemble_name_resolve does that:
      const char *real_name = targetm.strip_name_encoding (name);
      tree id = maybe_get_identifier (real_name);

      if (id)
        {
    ...
          mark_referenced (id);
    The intention is that assemble_external_libcall ensures the IDENTIFIER
    exists for the external libcall, then for actually emitted calls
    assemble_name_resolve sees those IDENTIFIERS and sets
TREE_SYMBOL_REFERENCED
    on them and finally process_pending_assemble_externals looks the
    IDENTIFIER up again and checks its TREE_SYMBOL_REFERENCED.

    But without the strip_name_encoding call, they can look up different
    identifiers and those are likely never used.

    In the PR, John was discussing whether get_identifier or
    maybe_get_identifier should be used, I believe in assemble_external_libcall
    we definitely want to use get_identifier, we need an IDENTIFIER allocated
    so that it can be actually tracked, in process_pending_assemble_externals
    it doesn't matter, the IDENTIFIER should be already created.

    2024-01-12  John David Anglin  <danglin@gcc.gnu.org>
                Jakub Jelinek  <jakub@redhat.com>

            PR middle-end/113182
            * varasm.cc (process_pending_assemble_externals,
            assemble_external_libcall): Use targetm.strip_name_encoding
            before calling get_identifier.

  parent reply	other threads:[~2024-01-12 12:59 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-30 18:03 [Bug other/113182] New: " danglin at gcc dot gnu.org
2023-12-30 18:30 ` [Bug middle-end/113182] " pinskia at gcc dot gnu.org
2023-12-30 18:38 ` dave.anglin at bell dot net
2023-12-30 19:19 ` danglin at gcc dot gnu.org
2023-12-30 19:26 ` danglin at gcc dot gnu.org
2024-01-01 20:41 ` danglin at gcc dot gnu.org
2024-01-08 14:19 ` rguenth at gcc dot gnu.org
2024-01-08 14:29 ` jakub at gcc dot gnu.org
2024-01-08 15:56 ` dave.anglin at bell dot net
2024-01-09 18:00 ` jakub at gcc dot gnu.org
2024-01-09 19:56 ` dave.anglin at bell dot net
2024-01-09 20:03 ` dave.anglin at bell dot net
2024-01-10 13:57 ` dave.anglin at bell dot net
2024-01-10 17:49 ` danglin at gcc dot gnu.org
2024-01-11 16:55 ` danglin at gcc dot gnu.org
2024-01-11 17:37 ` jakub at gcc dot gnu.org
2024-01-11 17:47 ` jakub at gcc dot gnu.org
2024-01-11 18:03 ` dave.anglin at bell dot net
2024-01-11 18:25 ` jakub at gcc dot gnu.org
2024-01-11 18:56 ` dave.anglin at bell dot net
2024-01-11 19:05 ` jakub at gcc dot gnu.org
2024-01-11 19:21 ` dave.anglin at bell dot net
2024-01-12 12:59 ` cvs-commit at gcc dot gnu.org [this message]
2024-01-12 13:06 ` jakub 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-113182-4-c9xR68ubcU@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).