From: John Wehle <john@feith.com>
To: rth@redhat.com
Cc: gcc@gcc.gnu.org
Subject: Re: alphaev6-dec-osf4.0f bootstrap failing due to constructor encoding
Date: Wed, 12 Sep 2001 11:30:00 -0000 [thread overview]
Message-ID: <200109121830.f8CIUUr16690@jwlab.FEITH.COM> (raw)
>> Why are they appended to the name of a constructor and how random
>> do the characters need to be?
>
> We need a unique symbol name. How can we acquire one? If there
> is a global symbol, then that symbol name must be unique, so we
> can generate one based on that. Otherwise...
Does the name have to be different each time the file is compiled, or
can we do something like append characters based on the file inode,
offset into the file, ... ? Something which results in the same encoding
each time that function in that file is compiled.
-- John
-------------------------------------------------------------------------
| Feith Systems | Voice: 1-215-646-8000 | Email: john@feith.com |
| John Wehle | Fax: 1-215-540-5495 | |
-------------------------------------------------------------------------
next reply other threads:[~2001-09-12 11:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-12 11:30 John Wehle [this message]
2001-09-12 12:30 ` Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2001-09-11 15:45 John Wehle
2001-09-12 10:00 ` Richard Henderson
2001-09-11 14:50 John Wehle
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=200109121830.f8CIUUr16690@jwlab.FEITH.COM \
--to=john@feith.com \
--cc=gcc@gcc.gnu.org \
--cc=rth@redhat.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).