From: Jeffrey A Law <law@cygnus.com>
To: Alexandre Oliva <oliva@dcc.unicamp.br>
Cc: Andrey Slepuhin <pooh@msu.ru>, dje@watson.ibm.com, egcs@cygnus.com
Subject: Re: Static symbols in libgcc
Date: Fri, 23 Jan 1998 13:30:00 -0000 [thread overview]
Message-ID: <27789.885523339@hurl.cygnus.com> (raw)
In-Reply-To: <orn2gpejzy.fsf@amazonas.dcc.unicamp.br>
In message < orn2gpejzy.fsf@amazonas.dcc.unicamp.br >you write:
> Jeffrey A Law writes:
>
> > 2. Move them into libstdc++. Shouldn't this just involve moving
> > some functions into libstdc++? Or to put it another way is
> > there some compelling reason to have these functions in libgcc?
>
> AFAIK, these variables are not exclusively used by the C++ front-end,
> so they shouldn't be moved into the C++-specific library. gcc 2.8.0
> was delayed that long in order to move exception handling into the
> back-end.
Good point.
> > 3. Declare them in such a way as to only get one copy; instead of
> > a static, can it be a global (yes, there's a namespace pollution
> > issue, but it's worth thinking about). It could even possibly
> > be made weak global if that helps.
>
> If it's named __gcc_something, it's not an issue, since this name is
> reserved, at least in the C language. Could this be a problem for
> other languages?
Right.
> > 4. Or have a global pointer to a runtime initialized data structure
> > which has the stuff we need. We have the capability to initialize
> > stuff at program startup, so it shouldn't be that much of a stretch
> > to use it for this purpose.
>
> I don't understand how functions would obtain references to this data
> structure. Wouldn't they need a global symbol or such?
Yes, it would be a single global (presumably exported) symbol.
jeff
prev parent reply other threads:[~1998-01-23 13:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-20 10:07 Jeffrey A Law
1998-01-22 2:29 ` Alexandre Oliva
1998-01-23 13:30 ` Jeffrey A Law [this message]
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=27789.885523339@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=dje@watson.ibm.com \
--cc=egcs@cygnus.com \
--cc=oliva@dcc.unicamp.br \
--cc=pooh@msu.ru \
/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).