This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [PATCH] Mitigate PR85222 a bit

From: Jonathan Wakely <jwakely dot gcc at gmail dot com>
To: Richard Biener <rguenther at suse dot de>
Cc: gcc-patches <gcc-patches at gcc dot gnu dot org>, "libstdc++" <libstdc++ at gcc dot gnu dot org>
Date: Fri, 6 Apr 2018 12:53:05 +0100
Subject: Re: [PATCH] Mitigate PR85222 a bit
References: <alpine.LSU.2.20.1804061131100.18265@zhemvz.fhfr.qr> <CAH6eHdTG3CfenOp=W2SbjcrNCYV25tP6SQBe+bZXK=Zh3h4jdw@mail.gmail.com> <alpine.LSU.2.20.1804061318430.18265@zhemvz.fhfr.qr> <CAH6eHdRM5L_eqEHb51vqmra53FcdRR_KR4mkj6_shQXnxXksjw@mail.gmail.com>

On 6 April 2018 at 12:48, Jonathan Wakely wrote:
> Currently --with-default-libstdcxx-abi doesn't alter the ABI of the
> shared lib when the dual-abi is enabled, just whether the initial
> value of the macro is 0 or 1. All the symbols in the library, and the
> type of exception thrown, are the same for every dual-abi build of the
> library.

I mean every dual-abi build for a given release, of course. Because
the type of exception thrown changed between gcc 6 and gcc 7, so maybe
my position that the option doesn't affect the ABI of the .so is
untenable, given that it changed independent of that option :-\

Follow-Ups:
- Re: [PATCH] Mitigate PR85222 a bit
  - From: Richard Biener

References:
- [PATCH] Mitigate PR85222 a bit
  - From: Richard Biener
- Re: [PATCH] Mitigate PR85222 a bit
  - From: Jonathan Wakely
- Re: [PATCH] Mitigate PR85222 a bit
  - From: Richard Biener
- Re: [PATCH] Mitigate PR85222 a bit
  - From: Jonathan Wakely

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