This is the mail archive of the gcc@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: C++98/C++11 ABI compatibility for gcc-4.7

From: Jeff Law <law at redhat dot com>
To: PaweÅ Sikora <pluto at agmk dot net>
Cc: gcc at gcc dot gnu dot org, Jonathan Wakely <jwakely dot gcc at gmail dot com>, James Y Knight <foom at fuhm dot net>, jyasskin at googlers dot com
Date: Thu, 14 Jun 2012 14:37:37 -0600
Subject: Re: C++98/C++11 ABI compatibility for gcc-4.7
References: <684e2daa82dfe58f3c0ca7898a646503.squirrel@fuhm.net> <CAH6eHdTEx0jgZWZJ8+RRhOEnD9zUXfLUPX30nhH8Zh6aYsE1Tg@mail.gmail.com> <CAH6eHdTMhoLvmoWZSCg3+1Gj1Z9p+EE=wwcvW86ubp9z9Ko3KQ@mail.gmail.com> <2194249.RI90jtvlYx@localhost>

On 06/14/2012 02:33 PM, PaweÅ Sikora wrote:


from the others side, someone can use -frecord-gcc-switches to detect mixed '-std=...'
after final linking and report error in such cases.

Given that we have -fabi= to go along with the -std= options, ISTM that we'd really be better off recording the ABI information in its own section rather than pull it out of the options section and that doing so should be the default rather than contingent on user options.

We'd then want some linker support to warn/error when attempts to mix-n-match are made.

jeff

References:
- Re: C++98/C++11 ABI compatibility for gcc-4.7
  - From: PaweÅ Sikora

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