public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dave.anglin at bell dot net" <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 18:56:13 +0000	[thread overview]
Message-ID: <bug-113182-4-3De8ETAFsT@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 #18 from dave.anglin at bell dot net ---
On 2024-01-11 1:25 p.m., jakub at gcc dot gnu.org wrote:
> The allocation is completely intentional, exactly to be able to track whether
> it was referenced or not.  Otherwise the exercise makes no sense.
In assemble_external_libcall, it's intentional.  But in
process_pending_assemble_externals,
all the allocations that are going to happen should have already happened.  It
is called in final.

When the name encoding wasn't stripped, get_identifier just created a new
identifier node that
wasn't referenced.  I tend to think there's a problem if the identifier node
doesn't already exist
in process_pending_assemble_externals.

  parent reply	other threads:[~2024-01-11 18:56 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 [this message]
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-3De8ETAFsT@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).