public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Iain Sandoe <iain@sandoe.co.uk>
To: Jason Merrill <jason@redhat.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH] c++, driver: Fix -static-libstdc++ for targets without Bstatic/dynamic.
Date: Thu, 22 Dec 2022 21:21:39 +0000	[thread overview]
Message-ID: <81F85096-E859-4D6B-8A6D-31802A864693@sandoe.co.uk> (raw)
In-Reply-To: <fafc6d9b-a479-e6af-c0a0-893ef7a6935d@redhat.com>



> On 22 Dec 2022, at 21:15, Jason Merrill <jason@redhat.com> wrote:
> 
> On 12/4/22 11:30, Iain Sandoe wrote:
>> This fixes a long-standing problem on Darwin where we cannot independently set
>> -static-libstdc++ because the flag gets stripped by the g++ driver.
>> This patch is essentially the same as the one used for the 'D' driver and has
>> been in local use for some time.  It has also been tested on Linux.
>> OK for master?
>> backports?
>> thanks
>> Iain
>> -- >8 --
>> The current implementation for swapping between the static and shared c++
>> runtimes relies on the static linker supporting Bstatic/dynamic which is
>> not available for every target (Darwin's linker does not support this).
>> Specs substitution (%s) is an alternative solution for this (which is what
>> Darwin uses for Fortran, D and Objective-C).  However, specs substitution
>> requires that the '-static-libstdc++' be preserved in the driver's command
>> line.  The patch here arranges for this to be done when the configuration
>> determines that linker support for Bstatic/dynamic is missing.
> 
> Would it work to define LIBSTDCXX_STATIC instead?

Not without modifying the build of libstdc++.  When Darwin’s linker sees a convenience library with the
same name as a shared one, it will pick the shared one, so we would have to modify the build of libstdc++
to make the library named libstdc++-static.a or so (that was essentially what the Apple gcc-4.2.1 impl.
did AFAIR).

>  If not, the patch is OK.

Thanks.

> 
> Really there should be a way for lang_specific_driver to mark a flag as "validated" rather than prune it.

Yes - especially since we now already three drivers (c++, d, gm2) that need to do the same stuff for
handing libstdc++.
Iain

> 
>> Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
>> gcc/cp/ChangeLog:
>> 	* g++spec.cc (lang_specific_driver): Preserve -static-libstdc++ in
>> 	the driver command line for targets without -Bstatic/dynamic support
>> 	in their static linker.
>> ---
>>  gcc/cp/g++spec.cc | 5 +++++
>>  1 file changed, 5 insertions(+)
>> diff --git a/gcc/cp/g++spec.cc b/gcc/cp/g++spec.cc
>> index 3d3b042dd56..f95d7965355 100644
>> --- a/gcc/cp/g++spec.cc
>> +++ b/gcc/cp/g++spec.cc
>> @@ -234,7 +234,12 @@ lang_specific_driver (struct cl_decoded_option **in_decoded_options,
>>    	case OPT_static_libstdc__:
>>  	  library = library >= 0 ? 2 : library;
>> +#ifdef HAVE_LD_STATIC_DYNAMIC
>> +	  /* Remove -static-libstdc++ from the command only if target supports
>> +	     LD_STATIC_DYNAMIC.  When not supported, it is left in so that a
>> +	     back-end target can use outfile substitution.  */
>>  	  args[i] |= SKIPOPT;
>> +#endif
>>  	  break;
>>    	case OPT_stdlib_:
> 


      reply	other threads:[~2022-12-22 21:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-04 16:30 Iain Sandoe
2022-12-22 19:14 ` [Ping^1] " Iain Sandoe
2022-12-22 21:15 ` Jason Merrill
2022-12-22 21:21   ` Iain Sandoe [this message]

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=81F85096-E859-4D6B-8A6D-31802A864693@sandoe.co.uk \
    --to=iain@sandoe.co.uk \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jason@redhat.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).