From: Gaius Mulley <gaiusmod2@gmail.com>
To: Iain Sandoe <iain@sandoe.co.uk>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 4/n] modula-2, driver: Handle static-libstd++ for targets without static/dynamic
Date: Thu, 05 Jan 2023 02:33:54 +0000 [thread overview]
Message-ID: <87o7rdpv59.fsf@debian> (raw)
In-Reply-To: <F3A9F9AF-50C4-410E-B21E-AFEAD722B3EF@sandoe.co.uk> (Iain Sandoe's message of "Fri, 30 Dec 2022 11:00:23 +0000")
Iain Sandoe <iain@sandoe.co.uk> writes:
> Oops pressed ‘send' too soon - this is part of the series for Darwin:
>
> There are several modula-2 issues on Darwin, some blocking bootstrap on
> one or more system versions.
>
> This has been tested on powerpc/i688-darwin9 .. x86_64-darwin10,17,21 and
> the prototype aarch64-darwin branch on darwin21.
>
> OK for trunk?
> thanks
> Iain
sure, LGTM
regards,
Gaius
>> On 30 Dec 2022, at 10:58, Iain Sandoe <iains.gcc@gmail.com> wrote:
>>
>> The follows the pattern used in C++ and D drivers to pass -static-libstdc++
>> onto the target driver to allow spec substitution of static libraries.
>>
>> NOTE: The general handling of Bstatic/dynamic and the possible use of static
>> libgm2 libraries is unimplemented in this driver so far. It seems likely
>> that the driver construction could be greatly simplified if the modula-2
>> runtimes were combined into fewer (hopefully, one) libraries.
>>
>> Signed-off-by: Iain Sandoe <iain@sandoe.co.uk>
>>
>> gcc/m2/ChangeLog:
>>
>> * gm2spec.cc (lang_specific_driver): Pass -static-libstdc++ on to
>> the target driver if the linker does not support Bstatic/dynamic.
>> ---
>> gcc/m2/gm2spec.cc | 5 +++++
>> 1 file changed, 5 insertions(+)
>>
>> diff --git a/gcc/m2/gm2spec.cc b/gcc/m2/gm2spec.cc
>> index 680dd3602ef..b9a5c4e79bb 100644
>> --- a/gcc/m2/gm2spec.cc
>> +++ b/gcc/m2/gm2spec.cc
>> @@ -767,7 +767,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_:
>> --
>> 2.37.1 (Apple Git-137.1)
>>
prev parent reply other threads:[~2023-01-05 2:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 10:58 Iain Sandoe
2022-12-30 11:00 ` Iain Sandoe
2023-01-05 2:33 ` Gaius Mulley [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=87o7rdpv59.fsf@debian \
--to=gaiusmod2@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=iain@sandoe.co.uk \
/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).