public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub 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: Thu, 11 Jan 2024 17:47:14 +0000 [thread overview] Message-ID: <bug-113182-4-bxdAxOzTob@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 #15 from Jakub Jelinek <jakub at gcc dot gnu.org> --- So, I'm going to bootstrap/regtest: 2024-01-11 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. --- gcc/varasm.cc.jj 2024-01-08 21:56:04.968516120 +0100 +++ gcc/varasm.cc 2024-01-11 18:44:19.171399167 +0100 @@ -2543,7 +2543,8 @@ process_pending_assemble_externals (void for (rtx list = pending_libcall_symbols; list; list = XEXP (list, 1)) { rtx symbol = XEXP (list, 0); - tree id = get_identifier (XSTR (symbol, 0)); + const char *name = targetm.strip_name_encoding (XSTR (symbol, 0)); + tree id = get_identifier (name); if (TREE_SYMBOL_REFERENCED (id)) targetm.asm_out.external_libcall (symbol); } @@ -2631,7 +2632,8 @@ assemble_external_libcall (rtx fun) reference to it will mark its tree node as referenced, via assemble_name_resolve. These are eventually emitted, if used, in process_pending_assemble_externals. */ - get_identifier (XSTR (fun, 0)); + const char *name = targetm.strip_name_encoding (XSTR (fun, 0)); + get_identifier (name); pending_libcall_symbols = gen_rtx_EXPR_LIST (VOIDmode, fun, pending_libcall_symbols); }
next prev parent reply other threads:[~2024-01-11 17:47 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 [this message] 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 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-bxdAxOzTob@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: linkBe 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).