From: Zack Weinberg <zack@codesourcery.com>
To: Mark Mitchell <mark@codesourcery.com>
Cc: Jan Hubicka <jh@suse.cz>, gcc@gcc.gnu.org
Subject: Re: Lazy allocation of DECL_ASSEMBLER_NAME
Date: Mon, 01 Mar 2004 21:19:00 -0000 [thread overview]
Message-ID: <87brngp8o0.fsf@egil.codesourcery.com> (raw)
In-Reply-To: <40439CBC.8070803@codesourcery.com> (Mark Mitchell's message of "Mon, 01 Mar 2004 12:27:40 -0800")
Mark Mitchell <mark@codesourcery.com> writes:
>>forward declarations and such, so single function got many DECLs.
>>Also we can't hash directly the addresses as the hashtable is saved into
>>PCH headers, so I am unsure about better sollution to the hashing.
>>I need at least one entity that is stable across PCH and multiple
>>declarations...
>>
> Use DECL_UID.
DECL_UID will not work - the multiple decls for the same symbol that we
currently have, they do not have the same DECL_UID (there is special
code in copy_node, merge_decls (C), duplicate_decls (C++) to ensure
that they do not).
zw
next prev parent reply other threads:[~2004-03-01 21:19 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-01 19:10 Mark Mitchell
2004-03-01 19:47 ` Geoff Keating
2004-03-01 19:57 ` Zack Weinberg
2004-03-01 20:21 ` Geoff Keating
2004-03-01 20:25 ` Mark Mitchell
2004-03-01 21:15 ` Zack Weinberg
2004-03-01 21:46 ` Geoff Keating
2004-03-01 22:03 ` Mark Mitchell
2004-03-01 22:54 ` Geoff Keating
2004-03-02 0:03 ` Mark Mitchell
2004-03-01 21:02 ` Dale Johannesen
2004-03-01 21:45 ` Mark Mitchell
2004-03-01 21:48 ` Dale Johannesen
2004-03-01 20:11 ` Mark Mitchell
2004-03-01 20:19 ` Zack Weinberg
2004-03-02 17:04 ` Mark Mitchell
2004-03-02 17:11 ` Jan Hubicka
2004-03-02 17:18 ` Mark Mitchell
2004-03-02 17:22 ` Jan Hubicka
2004-03-01 20:20 ` Jan Hubicka
2004-03-01 20:27 ` Mark Mitchell
2004-03-01 20:33 ` Jan Hubicka
2004-03-01 21:19 ` Geoff Keating
2004-03-01 21:19 ` Zack Weinberg [this message]
2004-03-01 22:21 Chris Lattner
2004-03-01 23:26 ` Mark Mitchell
2004-03-01 23:58 ` Chris Lattner
2004-03-02 0:09 ` Mark Mitchell
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=87brngp8o0.fsf@egil.codesourcery.com \
--to=zack@codesourcery.com \
--cc=gcc@gcc.gnu.org \
--cc=jh@suse.cz \
--cc=mark@codesourcery.com \
/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).