This is the mail archive of the libstdc++@gcc.gnu.org mailing list for the libstdc++ project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]

Re: Compiling w/o gcc?

To: Phil Edwards <pedwards at disaster dot jaj dot com>
Subject: Re: Compiling w/o gcc?
From: Jason Merrill <jason_merrill at redhat dot com>
Date: 06 Apr 2001 01:05:30 +0100
Cc: "David A. Greene" <greened at eecs dot umich dot edu>, libstdc++ at gcc dot gnu dot org
References: <200104010052.f310q5g07921@waller.constant.com><3AC88D1C.8050705@eecs.umich.edu><20010403161428.A2004@disaster.jaj.com><3AC95161.4010901@eecs.umich.edu><20010404163345.A6591@disaster.jaj.com>

>>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:

>> Obviously this is probably somewhat dangerous.  Are there
>> any known pitfalls with doing this?  It seems to me that as long as
>> I have headers that define the necessary bits (I do, from our vendor),
>> it should be ok to compile libstdc++ with those and link with the
>> vendor's runtime library.

> Exception handling might be very very funky.  Unless your vendor follows
> the same spec (which was designed to be vendor-neutral).

I wouldn't think so.  The library outside of libsupc++ should only rely on
standard C++ EH semantics.  Anything else is a bug.

Jason

References:
- Re: Compiling w/o gcc?
  - From: David A. Greene
- Re: Compiling w/o gcc?
  - From: Phil Edwards
- Re: Compiling w/o gcc?
  - From: David A. Greene
- Re: Compiling w/o gcc?
  - From: Phil Edwards

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]