From: Jason Merrill <jason@cygnus.com>
To: egcs@cygnus.com
Subject: Re: fixing the c++/f77 circular dependency
Date: Mon, 25 Aug 1997 18:32:36 -0000 [thread overview]
Message-ID: <m0x33vo-0004ecC@ocean.lucon.org> (raw)
Message-ID: <19970825183236.UM2QpkP_Oh5-2shZw4s8vCRbwliOe8RJJDyXPSpVv7w@z> (raw)
In-Reply-To: fixing the c++/f77 circular dependency
>>>>> Jim Wilson <wilson@cygnus.com> writes:
> I'd like to see them in libgcc.a. It should not be hard to put
> something in libgcc.a from cp/Makefile.
> I am not opposed to having C++ code in libgcc.a if it can be made to
> work. However, having already dealt with a number of problems resulting
> from this, I am skeptical that it can be made to work cleanly.
That may be. The code currently in libgcc is the freestanding library,
which includes some code called by various language constructs, and
therefore needs to be linked in automatically. I don't want people to have
to pull in libstdc++ to get RTTI support.
The only other option would seem to be a third library, linked in along
with libgcc. Then the trick is insinuating it into the specs file.
Jason
next reply other threads:[~1997-08-25 18:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-08-25 18:29 H.J. Lu [this message]
1997-08-25 18:32 ` Jason Merrill
1997-08-26 23:42 -g1 lossage Jeffrey A Law
1997-08-26 23:42 ` egcs release Jeffrey A Law
1997-08-27 6:01 Jim Wilson
1997-08-27 6:19 ` Jeffrey A Law
1997-08-27 22:01 Jim Wilson
1997-08-28 19:37 H.J. Lu
1997-08-28 20:03 suggested addition to -Wparentheses: warn about ` ! x & 1 ' Jim Meyering
1997-08-28 20:03 ` egcs release Jim Wilson
1997-08-29 6:00 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=m0x33vo-0004ecC@ocean.lucon.org \
--to=jason@cygnus.com \
--cc=egcs@cygnus.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).