From: Jeffrey A Law <law@cygnus.com>
To: svivanov@pdmi.ras.ru
Cc: egcs@cygnus.com
Subject: Re: Why link C with crtstuff? [patch]
Date: Sun, 26 Apr 1998 00:01:00 -0000 [thread overview]
Message-ID: <18449.893570733@hurl.cygnus.com> (raw)
In-Reply-To: <m0yTDf2-000B93C@svivano.pdmi.ras.ru>
In message < m0yTDf2-000B93C@svivano.pdmi.ras.ru >you write:
> There is a feature of egcs (and gcc 2.8.x) that I don't like.
> It links everything with crtbegin[S].o/crtend[S].o which in turn
> reference symbols from frame.o.
Well, like it or it, it will stay.
> On the other hand, crtstuff is a C++ related thing
> and is not needed for pure C code (AFAIK).
It is needed if:
* You want to link C & C++ together.
* You use exceptions.
* you use block profiling.
* You write code which uses the constructor or destructor
attributes.
* Shared libraries need to be self-contained in respect
to compiler intrinsics -- which include the EH mechanisms.
ie, the library must have its own copy of those routines.
Yes, this means we have to keep old interfaces for compiler
intrinsics around. But that's just the price we have to
pay.
jeff
next prev parent reply other threads:[~1998-04-26 0:01 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-25 17:40 Sergei Ivanov
1998-04-26 0:01 ` Jeffrey A Law [this message]
1998-04-26 0:19 ` H.J. Lu
1998-04-26 10:05 ` Jeffrey A Law
1998-04-26 10:26 ` H.J. Lu
1998-04-26 12:08 ` Ian Lance Taylor
1998-04-26 12:45 ` Sergei Ivanov
[not found] <m0yTYbl-000598C@ocean.lucon.org>
1998-04-26 17:15 ` Sergei Ivanov
1998-04-26 21:56 ` H.J. Lu
1998-04-27 13:59 ` Sergei Ivanov
[not found] <m0yU6e1-000B93C@svivano.pdmi.ras.ru>
1998-04-28 14:10 ` H.J. Lu
1998-04-28 10:26 ` Ian Lance Taylor
1998-04-28 10:47 ` H.J. Lu
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=18449.893570733@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=svivanov@pdmi.ras.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).