| Message ID | 20221121072526.103446-1-sebastian.huber@embedded-brains.de |
|---|---|
| State | New |
| Headers |
Return-Path: <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 17F2D3851882 for <patchwork@sourceware.org>; Mon, 21 Nov 2022 07:26:19 +0000 (GMT) X-Original-To: gcc-patches@gcc.gnu.org Delivered-To: gcc-patches@gcc.gnu.org Received: from dedi548.your-server.de (dedi548.your-server.de [85.10.215.148]) by sourceware.org (Postfix) with ESMTPS id 34A7A3899435 for <gcc-patches@gcc.gnu.org>; Mon, 21 Nov 2022 07:25:33 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 34A7A3899435 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=embedded-brains.de Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=embedded-brains.de Received: from sslproxy06.your-server.de ([78.46.172.3]) by dedi548.your-server.de with esmtpsa (TLS1.3) tls TLS_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <sebastian.huber@embedded-brains.de>) id 1ox1BL-000KXy-LD; Mon, 21 Nov 2022 08:25:31 +0100 Received: from [82.100.198.138] (helo=mail.embedded-brains.de) by sslproxy06.your-server.de with esmtpsa (TLSv1.3:TLS_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from <sebastian.huber@embedded-brains.de>) id 1ox1BL-000TRy-Ia; Mon, 21 Nov 2022 08:25:31 +0100 Received: from localhost (localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id 43B894800B4; Mon, 21 Nov 2022 08:25:31 +0100 (CET) Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 6xeH3em-gPn5; Mon, 21 Nov 2022 08:25:30 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mail.embedded-brains.de (Postfix) with ESMTP id BC9DA4801C9; Mon, 21 Nov 2022 08:25:30 +0100 (CET) X-Virus-Scanned: amavisd-new at zimbra.eb.localhost Received: from mail.embedded-brains.de ([127.0.0.1]) by localhost (zimbra.eb.localhost [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Aj6_S7gCUgEL; Mon, 21 Nov 2022 08:25:30 +0100 (CET) Received: from zimbra.eb.localhost (unknown [192.168.96.242]) by mail.embedded-brains.de (Postfix) with ESMTPSA id 9CB4E4800B4; Mon, 21 Nov 2022 08:25:30 +0100 (CET) From: Sebastian Huber <sebastian.huber@embedded-brains.de> To: gcc-patches@gcc.gnu.org Cc: Jeff Law <jeffreyalaw@gmail.com> Subject: [PATCH v2 1/2] Allow subtarget customization of CC1_SPEC Date: Mon, 21 Nov 2022 08:25:25 +0100 Message-Id: <20221121072526.103446-1-sebastian.huber@embedded-brains.de> X-Mailer: git-send-email 2.35.3 MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable X-Authenticated-Sender: smtp-embedded@poldinet.de X-Virus-Scanned: Clear (ClamAV 0.103.7/26726/Sun Nov 20 09:50:39 2022) X-Spam-Status: No, score=-11.5 required=5.0 tests=BAYES_00, GIT_PATCH_0, KAM_DMARC_STATUS, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org X-BeenThere: gcc-patches@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-patches mailing list <gcc-patches.gcc.gnu.org> List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=unsubscribe> List-Archive: <https://gcc.gnu.org/pipermail/gcc-patches/> List-Post: <mailto:gcc-patches@gcc.gnu.org> List-Help: <mailto:gcc-patches-request@gcc.gnu.org?subject=help> List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-patches>, <mailto:gcc-patches-request@gcc.gnu.org?subject=subscribe> Errors-To: gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org Sender: "Gcc-patches" <gcc-patches-bounces+patchwork=sourceware.org@gcc.gnu.org> |
| Series |
[v2,1/2] Allow subtarget customization of CC1_SPEC
|
|
Commit Message
Sebastian Huber
Nov. 21, 2022, 7:25 a.m. UTC
gcc/ChangeLog:
* gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined.
(cc1_spec): Append SUBTARGET_CC1_SPEC.
---
v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC.
This avoids having to modify all the CC1_SPEC definitions in the targets.
gcc/gcc.cc | 9 ++++++++-
1 file changed, 8 insertions(+), 1 deletion(-)
Comments
Hi! I suppose I just fail to see some detail here, but: On 2022-11-21T08:25:25+0100, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote: > gcc/ChangeLog: > > * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined. > (cc1_spec): Append SUBTARGET_CC1_SPEC. > --- > v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC. > This avoids having to modify all the CC1_SPEC definitions in the targets. > > gcc/gcc.cc | 9 ++++++++- > 1 file changed, 8 insertions(+), 1 deletion(-) > > diff --git a/gcc/gcc.cc b/gcc/gcc.cc > index 830ab88701f..4e1574a4df1 100644 > --- a/gcc/gcc.cc > +++ b/gcc/gcc.cc > @@ -706,6 +706,13 @@ proper position among the other output files. */ > #define CPP_SPEC "" > #endif > > +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and > + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended > + to CC1_SPEC. */ > +#ifndef SUBTARGET_CC1_SPEC > +#define SUBTARGET_CC1_SPEC "" > +#endif > + > /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus > or extra switch-translations. */ > #ifndef CC1_SPEC > @@ -1174,7 +1181,7 @@ proper position among the other output files. */ > static const char *asm_debug = ASM_DEBUG_SPEC; > static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; > static const char *cpp_spec = CPP_SPEC; > -static const char *cc1_spec = CC1_SPEC; > +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; > static const char *cc1plus_spec = CC1PLUS_SPEC; > static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; > static const char *link_ssp_spec = LINK_SSP_SPEC; ... doesn't this (at least potentially?) badly interact with any existing 'SUBTARGET_CC1_SPEC' definitions -- which pe rabove get appended to 'cc1_spec'? gcc/config/loongarch/gnu-user.h- and provides this hook instead. */ gcc/config/loongarch/gnu-user.h:#undef SUBTARGET_CC1_SPEC gcc/config/loongarch/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC gcc/config/loongarch/gnu-user.h- -- gcc/config/loongarch/loongarch.h-#define EXTRA_SPECS \ gcc/config/loongarch/loongarch.h: {"subtarget_cc1_spec", SUBTARGET_CC1_SPEC}, \ gcc/config/loongarch/loongarch.h- {"subtarget_cpp_spec", SUBTARGET_CPP_SPEC}, \ -- gcc/config/mips/gnu-user.h- and provides this hook instead. */ gcc/config/mips/gnu-user.h:#undef SUBTARGET_CC1_SPEC gcc/config/mips/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC gcc/config/mips/gnu-user.h- -- gcc/config/mips/linux-common.h- gcc/config/mips/linux-common.h:#undef SUBTARGET_CC1_SPEC gcc/config/mips/linux-common.h:#define SUBTARGET_CC1_SPEC \ gcc/config/mips/linux-common.h- LINUX_OR_ANDROID_CC (GNU_USER_TARGET_CC1_SPEC, \ -- gcc/config/mips/mips.h- gcc/config/mips/mips.h:/* SUBTARGET_CC1_SPEC is passed to the compiler proper. It may be gcc/config/mips/mips.h- overridden by subtargets. */ gcc/config/mips/mips.h:#ifndef SUBTARGET_CC1_SPEC gcc/config/mips/mips.h:#define SUBTARGET_CC1_SPEC "" gcc/config/mips/mips.h-#endif -- gcc/config/mips/mips.h-#define EXTRA_SPECS \ gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ gcc/config/mips/mips.h- { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ -- gcc/config/mips/r3900.h-/* By default (if not mips-something-else) produce code for the r3900 */ gcc/config/mips/r3900.h:#undef SUBTARGET_CC1_SPEC gcc/config/mips/r3900.h:#define SUBTARGET_CC1_SPEC "\ gcc/config/mips/r3900.h-%{mhard-float:%e-mhard-float not supported} \ Grüße Thomas ----------------- Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
On 06.12.22 22:06, Thomas Schwinge wrote: > Hi! > > I suppose I just fail to see some detail here, but: > > On 2022-11-21T08:25:25+0100, Sebastian Huber<sebastian.huber@embedded-brains.de> wrote: >> gcc/ChangeLog: >> >> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined. >> (cc1_spec): Append SUBTARGET_CC1_SPEC. >> --- >> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC. >> This avoids having to modify all the CC1_SPEC definitions in the targets. >> >> gcc/gcc.cc | 9 ++++++++- >> 1 file changed, 8 insertions(+), 1 deletion(-) >> >> diff --git a/gcc/gcc.cc b/gcc/gcc.cc >> index 830ab88701f..4e1574a4df1 100644 >> --- a/gcc/gcc.cc >> +++ b/gcc/gcc.cc >> @@ -706,6 +706,13 @@ proper position among the other output files. */ >> #define CPP_SPEC "" >> #endif >> >> +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and >> + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended >> + to CC1_SPEC. */ >> +#ifndef SUBTARGET_CC1_SPEC >> +#define SUBTARGET_CC1_SPEC "" >> +#endif >> + >> /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus >> or extra switch-translations. */ >> #ifndef CC1_SPEC >> @@ -1174,7 +1181,7 @@ proper position among the other output files. */ >> static const char *asm_debug = ASM_DEBUG_SPEC; >> static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; >> static const char *cpp_spec = CPP_SPEC; >> -static const char *cc1_spec = CC1_SPEC; >> +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; >> static const char *cc1plus_spec = CC1PLUS_SPEC; >> static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; >> static const char *link_ssp_spec = LINK_SSP_SPEC; > ... doesn't this (at least potentially?) badly interact with any existing > 'SUBTARGET_CC1_SPEC' definitions -- which pe rabove get appended to > 'cc1_spec'? > > gcc/config/loongarch/gnu-user.h- and provides this hook instead. */ > gcc/config/loongarch/gnu-user.h:#undef SUBTARGET_CC1_SPEC > gcc/config/loongarch/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC > gcc/config/loongarch/gnu-user.h- > -- > gcc/config/loongarch/loongarch.h-#define EXTRA_SPECS \ > gcc/config/loongarch/loongarch.h: {"subtarget_cc1_spec", SUBTARGET_CC1_SPEC}, \ > gcc/config/loongarch/loongarch.h- {"subtarget_cpp_spec", SUBTARGET_CPP_SPEC}, \ > -- > gcc/config/mips/gnu-user.h- and provides this hook instead. */ > gcc/config/mips/gnu-user.h:#undef SUBTARGET_CC1_SPEC > gcc/config/mips/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC > gcc/config/mips/gnu-user.h- > -- > gcc/config/mips/linux-common.h- > gcc/config/mips/linux-common.h:#undef SUBTARGET_CC1_SPEC > gcc/config/mips/linux-common.h:#define SUBTARGET_CC1_SPEC \ > gcc/config/mips/linux-common.h- LINUX_OR_ANDROID_CC (GNU_USER_TARGET_CC1_SPEC, \ > -- > gcc/config/mips/mips.h- > gcc/config/mips/mips.h:/* SUBTARGET_CC1_SPEC is passed to the compiler proper. It may be > gcc/config/mips/mips.h- overridden by subtargets. */ > gcc/config/mips/mips.h:#ifndef SUBTARGET_CC1_SPEC > gcc/config/mips/mips.h:#define SUBTARGET_CC1_SPEC "" > gcc/config/mips/mips.h-#endif > -- > gcc/config/mips/mips.h-#define EXTRA_SPECS \ > gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ > gcc/config/mips/mips.h- { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ > -- > gcc/config/mips/r3900.h-/* By default (if not mips-something-else) produce code for the r3900 */ > gcc/config/mips/r3900.h:#undef SUBTARGET_CC1_SPEC > gcc/config/mips/r3900.h:#define SUBTARGET_CC1_SPEC "\ > gcc/config/mips/r3900.h-%{mhard-float:%e-mhard-float not supported} \ Oh, I came up with the name SUBTARGET_CC1_SPEC after a discussion on the mailing list and I have to admit that I didn't check that it was actually already in use. What about renaming the loongarch/mips define to LOONGARCH_CC1_SPEC and MIPS_CC1_SPEC?
Hi! On 2022-12-07T07:04:10+0100, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote: > On 06.12.22 22:06, Thomas Schwinge wrote: > I suppose I just fail to see some detail here, but: > >> On 2022-11-21T08:25:25+0100, Sebastian Huber<sebastian.huber@embedded-brains.de> wrote: >>> gcc/ChangeLog: >>> >>> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined. >>> (cc1_spec): Append SUBTARGET_CC1_SPEC. >>> --- >>> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC. >>> This avoids having to modify all the CC1_SPEC definitions in the targets. >>> >>> gcc/gcc.cc | 9 ++++++++- >>> 1 file changed, 8 insertions(+), 1 deletion(-) >>> >>> diff --git a/gcc/gcc.cc b/gcc/gcc.cc >>> index 830ab88701f..4e1574a4df1 100644 >>> --- a/gcc/gcc.cc >>> +++ b/gcc/gcc.cc >>> @@ -706,6 +706,13 @@ proper position among the other output files. */ >>> #define CPP_SPEC "" >>> #endif >>> >>> +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and >>> + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended >>> + to CC1_SPEC. */ >>> +#ifndef SUBTARGET_CC1_SPEC >>> +#define SUBTARGET_CC1_SPEC "" >>> +#endif >>> + >>> /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus >>> or extra switch-translations. */ >>> #ifndef CC1_SPEC >>> @@ -1174,7 +1181,7 @@ proper position among the other output files. */ >>> static const char *asm_debug = ASM_DEBUG_SPEC; >>> static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; >>> static const char *cpp_spec = CPP_SPEC; >>> -static const char *cc1_spec = CC1_SPEC; >>> +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; >>> static const char *cc1plus_spec = CC1PLUS_SPEC; >>> static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; >>> static const char *link_ssp_spec = LINK_SSP_SPEC; >> >> ... doesn't this (at least potentially?) badly interact with any existing >> 'SUBTARGET_CC1_SPEC' definitions -- which pe rabove get appended to >> 'cc1_spec'? >> >> gcc/config/loongarch/gnu-user.h- and provides this hook instead. */ >> gcc/config/loongarch/gnu-user.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/loongarch/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >> gcc/config/loongarch/gnu-user.h- >> -- >> gcc/config/loongarch/loongarch.h-#define EXTRA_SPECS \ >> gcc/config/loongarch/loongarch.h: {"subtarget_cc1_spec", SUBTARGET_CC1_SPEC}, \ >> gcc/config/loongarch/loongarch.h- {"subtarget_cpp_spec", SUBTARGET_CPP_SPEC}, \ >> -- >> gcc/config/mips/gnu-user.h- and provides this hook instead. */ >> gcc/config/mips/gnu-user.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/mips/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >> gcc/config/mips/gnu-user.h- >> -- >> gcc/config/mips/linux-common.h- >> gcc/config/mips/linux-common.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/mips/linux-common.h:#define SUBTARGET_CC1_SPEC \ >> gcc/config/mips/linux-common.h- LINUX_OR_ANDROID_CC (GNU_USER_TARGET_CC1_SPEC, \ >> -- >> gcc/config/mips/mips.h- >> gcc/config/mips/mips.h:/* SUBTARGET_CC1_SPEC is passed to the compiler proper. It may be >> gcc/config/mips/mips.h- overridden by subtargets. */ >> gcc/config/mips/mips.h:#ifndef SUBTARGET_CC1_SPEC >> gcc/config/mips/mips.h:#define SUBTARGET_CC1_SPEC "" >> gcc/config/mips/mips.h-#endif >> -- >> gcc/config/mips/mips.h-#define EXTRA_SPECS \ >> gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ >> gcc/config/mips/mips.h- { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ >> -- >> gcc/config/mips/r3900.h-/* By default (if not mips-something-else) produce code for the r3900 */ >> gcc/config/mips/r3900.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/mips/r3900.h:#define SUBTARGET_CC1_SPEC "\ >> gcc/config/mips/r3900.h-%{mhard-float:%e-mhard-float not supported} \ > > Oh, I came up with the name SUBTARGET_CC1_SPEC after a discussion on the > mailing list I've put Iain in CC. > and I have to admit that I didn't check that it was > actually already in use. Always one of the first things I do. ;-) > What about renaming the loongarch/mips define > to LOONGARCH_CC1_SPEC and MIPS_CC1_SPEC? Also in use are a number of other 'SUBTARGET_[...]_SPEC' and corresponding 'subtarget_[...]_spec' in 'EXTRA_SPECS', for example: gcc/config/mips/mips.h-#define EXTRA_SPECS \ gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ gcc/config/mips/mips.h: { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ gcc/config/mips/mips.h: { "subtarget_asm_debugging_spec", SUBTARGET_ASM_DEBUGGING_SPEC }, \ gcc/config/mips/mips.h: { "subtarget_asm_spec", SUBTARGET_ASM_SPEC }, \ gcc/config/mips/mips.h- { "asm_abi_default_spec", "-" MULTILIB_ABI_DEFAULT }, \ gcc/config/mips/mips.h- { "endian_spec", ENDIAN_SPEC }, \ gcc/config/mips/mips.h: SUBTARGET_EXTRA_SPECS Do we need/want to keep the association of same-name upper-case/lower-case variants; in your proposal you'd then get '{ "subtarget_cc1_spec", MIPS_CC1_SPEC }', for example? (I didn't quickly grok all 'EXTRA_SPECS' usage.) Alternatively, what about renaming your 'SUBTARGET_CC1_SPEC' to 'CC1_SPEC_EXTRA' -- if that makes sense? static const char *cc1_spec = CC1_SPEC CC1_SPEC_EXTRA; But doesn't somehow this whole thing feel a bit like "chating the system"? ;-) Can't you actually achieve your thing (TLS model) via (new) 'EXTRA_SPECS' in 'gcc/config/rtems.h', for example? Grüße Thomas ----------------- Siemens Electronic Design Automation GmbH; Anschrift: Arnulfstraße 201, 80634 München; Gesellschaft mit beschränkter Haftung; Geschäftsführer: Thomas Heurung, Frank Thürauf; Sitz der Gesellschaft: München; Registergericht München, HRB 106955
On 07.12.22 08:10, Thomas Schwinge wrote: > Hi! > > On 2022-12-07T07:04:10+0100, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote: >> On 06.12.22 22:06, Thomas Schwinge wrote: >> I suppose I just fail to see some detail here, but: >> >>> On 2022-11-21T08:25:25+0100, Sebastian Huber<sebastian.huber@embedded-brains.de> wrote: >>>> gcc/ChangeLog: >>>> >>>> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined. >>>> (cc1_spec): Append SUBTARGET_CC1_SPEC. >>>> --- >>>> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC. >>>> This avoids having to modify all the CC1_SPEC definitions in the targets. >>>> >>>> gcc/gcc.cc | 9 ++++++++- >>>> 1 file changed, 8 insertions(+), 1 deletion(-) >>>> >>>> diff --git a/gcc/gcc.cc b/gcc/gcc.cc >>>> index 830ab88701f..4e1574a4df1 100644 >>>> --- a/gcc/gcc.cc >>>> +++ b/gcc/gcc.cc >>>> @@ -706,6 +706,13 @@ proper position among the other output files. */ >>>> #define CPP_SPEC "" >>>> #endif >>>> >>>> +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and >>>> + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended >>>> + to CC1_SPEC. */ >>>> +#ifndef SUBTARGET_CC1_SPEC >>>> +#define SUBTARGET_CC1_SPEC "" >>>> +#endif >>>> + >>>> /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus >>>> or extra switch-translations. */ >>>> #ifndef CC1_SPEC >>>> @@ -1174,7 +1181,7 @@ proper position among the other output files. */ >>>> static const char *asm_debug = ASM_DEBUG_SPEC; >>>> static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; >>>> static const char *cpp_spec = CPP_SPEC; >>>> -static const char *cc1_spec = CC1_SPEC; >>>> +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; >>>> static const char *cc1plus_spec = CC1PLUS_SPEC; >>>> static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; >>>> static const char *link_ssp_spec = LINK_SSP_SPEC; >>> >>> ... doesn't this (at least potentially?) badly interact with any existing >>> 'SUBTARGET_CC1_SPEC' definitions -- which pe rabove get appended to >>> 'cc1_spec'? >>> >>> gcc/config/loongarch/gnu-user.h- and provides this hook instead. */ >>> gcc/config/loongarch/gnu-user.h:#undef SUBTARGET_CC1_SPEC >>> gcc/config/loongarch/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >>> gcc/config/loongarch/gnu-user.h- >>> -- >>> gcc/config/loongarch/loongarch.h-#define EXTRA_SPECS \ >>> gcc/config/loongarch/loongarch.h: {"subtarget_cc1_spec", SUBTARGET_CC1_SPEC}, \ >>> gcc/config/loongarch/loongarch.h- {"subtarget_cpp_spec", SUBTARGET_CPP_SPEC}, \ >>> -- >>> gcc/config/mips/gnu-user.h- and provides this hook instead. */ >>> gcc/config/mips/gnu-user.h:#undef SUBTARGET_CC1_SPEC >>> gcc/config/mips/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >>> gcc/config/mips/gnu-user.h- >>> -- >>> gcc/config/mips/linux-common.h- >>> gcc/config/mips/linux-common.h:#undef SUBTARGET_CC1_SPEC >>> gcc/config/mips/linux-common.h:#define SUBTARGET_CC1_SPEC \ >>> gcc/config/mips/linux-common.h- LINUX_OR_ANDROID_CC (GNU_USER_TARGET_CC1_SPEC, \ >>> -- >>> gcc/config/mips/mips.h- >>> gcc/config/mips/mips.h:/* SUBTARGET_CC1_SPEC is passed to the compiler proper. It may be >>> gcc/config/mips/mips.h- overridden by subtargets. */ >>> gcc/config/mips/mips.h:#ifndef SUBTARGET_CC1_SPEC >>> gcc/config/mips/mips.h:#define SUBTARGET_CC1_SPEC "" >>> gcc/config/mips/mips.h-#endif >>> -- >>> gcc/config/mips/mips.h-#define EXTRA_SPECS \ >>> gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ >>> gcc/config/mips/mips.h- { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ >>> -- >>> gcc/config/mips/r3900.h-/* By default (if not mips-something-else) produce code for the r3900 */ >>> gcc/config/mips/r3900.h:#undef SUBTARGET_CC1_SPEC >>> gcc/config/mips/r3900.h:#define SUBTARGET_CC1_SPEC "\ >>> gcc/config/mips/r3900.h-%{mhard-float:%e-mhard-float not supported} \ >> >> Oh, I came up with the name SUBTARGET_CC1_SPEC after a discussion on the >> mailing list > > I've put Iain in CC. > >> and I have to admit that I didn't check that it was >> actually already in use. > > Always one of the first things I do. ;-) > >> What about renaming the loongarch/mips define >> to LOONGARCH_CC1_SPEC and MIPS_CC1_SPEC? > > Also in use are a number of other 'SUBTARGET_[...]_SPEC' and > corresponding 'subtarget_[...]_spec' in 'EXTRA_SPECS', for example: > > gcc/config/mips/mips.h-#define EXTRA_SPECS \ > gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ > gcc/config/mips/mips.h: { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ > gcc/config/mips/mips.h: { "subtarget_asm_debugging_spec", SUBTARGET_ASM_DEBUGGING_SPEC }, \ > gcc/config/mips/mips.h: { "subtarget_asm_spec", SUBTARGET_ASM_SPEC }, \ > gcc/config/mips/mips.h- { "asm_abi_default_spec", "-" MULTILIB_ABI_DEFAULT }, \ > gcc/config/mips/mips.h- { "endian_spec", ENDIAN_SPEC }, \ > gcc/config/mips/mips.h: SUBTARGET_EXTRA_SPECS > > Do we need/want to keep the association of same-name > upper-case/lower-case variants; in your proposal you'd then get > '{ "subtarget_cc1_spec", MIPS_CC1_SPEC }', for example? (I didn't > quickly grok all 'EXTRA_SPECS' usage.) > > Alternatively, what about renaming your 'SUBTARGET_CC1_SPEC' to > 'CC1_SPEC_EXTRA' -- if that makes sense? > > static const char *cc1_spec = CC1_SPEC CC1_SPEC_EXTRA; I was told that an operating system is the subtarget in this context. So from the name SUBTARGET_CC1_SPEC is is clear who is in charge. This is not clear from CC1_SPEC_EXTRA. > > But doesn't somehow this whole thing feel a bit like "chating the > system"? ;-) > > Can't you actually achieve your thing (TLS model) via (new) 'EXTRA_SPECS' > in 'gcc/config/rtems.h', for example? The EXTRA_SPECS definition seems to be target-specific. Not all targets let an operating system define SUBTARGET_EXTRA_SPECS. The SUBTARGET_EXTRA_SPECS would need to get propagated to the corresponding specs, which seems to be also target-specific, for example for mips we have: #undef CC1_SPEC #define CC1_SPEC "\ %{G*} %{EB:-meb} %{EL:-mel} %{EB:%{EL:%emay not use both -EB and -EL}} \ %(subtarget_cc1_spec)" I think going this route would lead to a lot of changes affecting all targets.
Hi > On 7 Dec 2022, at 07:54, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote: > > > > On 07.12.22 08:10, Thomas Schwinge wrote: >> Hi! >> On 2022-12-07T07:04:10+0100, Sebastian Huber <sebastian.huber@embedded-brains.de> wrote: >>> On 06.12.22 22:06, Thomas Schwinge wrote: >>> I suppose I just fail to see some detail here, but: >>> >>>> On 2022-11-21T08:25:25+0100, Sebastian Huber<sebastian.huber@embedded-brains.de> wrote: >>>>> gcc/ChangeLog: >>>>> >>>>> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined. >>>>> (cc1_spec): Append SUBTARGET_CC1_SPEC. >>>>> --- >>>>> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC. >>>>> This avoids having to modify all the CC1_SPEC definitions in the targets. >>>>> >>>>> gcc/gcc.cc | 9 ++++++++- >>>>> 1 file changed, 8 insertions(+), 1 deletion(-) >>>>> >>>>> diff --git a/gcc/gcc.cc b/gcc/gcc.cc >>>>> index 830ab88701f..4e1574a4df1 100644 >>>>> --- a/gcc/gcc.cc >>>>> +++ b/gcc/gcc.cc >>>>> @@ -706,6 +706,13 @@ proper position among the other output files. */ >>>>> #define CPP_SPEC "" >>>>> #endif >>>>> >>>>> +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and >>>>> + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended >>>>> + to CC1_SPEC. */ >>>>> +#ifndef SUBTARGET_CC1_SPEC >>>>> +#define SUBTARGET_CC1_SPEC "" >>>>> +#endif >>>>> + >>>>> /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus >>>>> or extra switch-translations. */ >>>>> #ifndef CC1_SPEC >>>>> @@ -1174,7 +1181,7 @@ proper position among the other output files. */ >>>>> static const char *asm_debug = ASM_DEBUG_SPEC; >>>>> static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; >>>>> static const char *cpp_spec = CPP_SPEC; >>>>> -static const char *cc1_spec = CC1_SPEC; >>>>> +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; >>>>> static const char *cc1plus_spec = CC1PLUS_SPEC; >>>>> static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; >>>>> static const char *link_ssp_spec = LINK_SSP_SPEC; >>>> >>>> ... doesn't this (at least potentially?) badly interact with any existing >>>> 'SUBTARGET_CC1_SPEC' definitions -- which pe rabove get appended to >>>> 'cc1_spec'? >>>> >>>> gcc/config/loongarch/gnu-user.h- and provides this hook instead. */ >>>> gcc/config/loongarch/gnu-user.h:#undef SUBTARGET_CC1_SPEC >>>> gcc/config/loongarch/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >>>> gcc/config/loongarch/gnu-user.h- >>>> -- >>>> gcc/config/loongarch/loongarch.h-#define EXTRA_SPECS \ >>>> gcc/config/loongarch/loongarch.h: {"subtarget_cc1_spec", SUBTARGET_CC1_SPEC}, \ >>>> gcc/config/loongarch/loongarch.h- {"subtarget_cpp_spec", SUBTARGET_CPP_SPEC}, \ >>>> -- >>>> gcc/config/mips/gnu-user.h- and provides this hook instead. */ >>>> gcc/config/mips/gnu-user.h:#undef SUBTARGET_CC1_SPEC >>>> gcc/config/mips/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >>>> gcc/config/mips/gnu-user.h- >>>> -- >>>> gcc/config/mips/linux-common.h- >>>> gcc/config/mips/linux-common.h:#undef SUBTARGET_CC1_SPEC >>>> gcc/config/mips/linux-common.h:#define SUBTARGET_CC1_SPEC \ >>>> gcc/config/mips/linux-common.h- LINUX_OR_ANDROID_CC (GNU_USER_TARGET_CC1_SPEC, \ >>>> -- >>>> gcc/config/mips/mips.h- >>>> gcc/config/mips/mips.h:/* SUBTARGET_CC1_SPEC is passed to the compiler proper. It may be >>>> gcc/config/mips/mips.h- overridden by subtargets. */ >>>> gcc/config/mips/mips.h:#ifndef SUBTARGET_CC1_SPEC >>>> gcc/config/mips/mips.h:#define SUBTARGET_CC1_SPEC "" >>>> gcc/config/mips/mips.h-#endif >>>> -- >>>> gcc/config/mips/mips.h-#define EXTRA_SPECS \ >>>> gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ >>>> gcc/config/mips/mips.h- { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ >>>> -- >>>> gcc/config/mips/r3900.h-/* By default (if not mips-something-else) produce code for the r3900 */ >>>> gcc/config/mips/r3900.h:#undef SUBTARGET_CC1_SPEC >>>> gcc/config/mips/r3900.h:#define SUBTARGET_CC1_SPEC "\ >>>> gcc/config/mips/r3900.h-%{mhard-float:%e-mhard-float not supported} \ >>> >>> Oh, I came up with the name SUBTARGET_CC1_SPEC after a discussion on the >>> mailing list >> I've put Iain in CC. >>> and I have to admit that I didn't check that it was >>> actually already in use. >> Always one of the first things I do. ;-) >>> What about renaming the loongarch/mips define >>> to LOONGARCH_CC1_SPEC and MIPS_CC1_SPEC? >> Also in use are a number of other 'SUBTARGET_[...]_SPEC' and >> corresponding 'subtarget_[...]_spec' in 'EXTRA_SPECS', for example: >> gcc/config/mips/mips.h-#define EXTRA_SPECS \ >> gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ >> gcc/config/mips/mips.h: { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ >> gcc/config/mips/mips.h: { "subtarget_asm_debugging_spec", SUBTARGET_ASM_DEBUGGING_SPEC }, \ >> gcc/config/mips/mips.h: { "subtarget_asm_spec", SUBTARGET_ASM_SPEC }, \ >> gcc/config/mips/mips.h- { "asm_abi_default_spec", "-" MULTILIB_ABI_DEFAULT }, \ >> gcc/config/mips/mips.h- { "endian_spec", ENDIAN_SPEC }, \ >> gcc/config/mips/mips.h: SUBTARGET_EXTRA_SPECS >> Do we need/want to keep the association of same-name >> upper-case/lower-case variants; in your proposal you'd then get >> '{ "subtarget_cc1_spec", MIPS_CC1_SPEC }', for example? (I didn't >> quickly grok all 'EXTRA_SPECS' usage.) >> Alternatively, what about renaming your 'SUBTARGET_CC1_SPEC' to >> 'CC1_SPEC_EXTRA' -- if that makes sense? >> static const char *cc1_spec = CC1_SPEC CC1_SPEC_EXTRA; > > I was told that an operating system is the subtarget in this context. So from the name SUBTARGET_CC1_SPEC is is clear who is in charge. This is not clear from CC1_SPEC_EXTRA. Perhaps I was not precise enough (or misunderstood the full requirement). Having reloaded some state on this thread… * The initial point was that target specs were an alternate mechanism for doing what was required which I understood to be that there was "an OS-specific common spec that needed to be added to multiple ports". * There are existing cases (at least Darwin is one) where this is done - multiple ports (e.g. x86, rs6000) refer to common specs in the gcc/config/ - so, for example, the specs in gcc/config/i386/darwin.h pull in common specs from gcc/config/darwin.h * there are also cases where this is specifically done in port code (sometimes with “SUBSUBTARGET_xxxx”) === I made the comment that, IMO this is initially confusing when the OS might be considered the target and the ISA the sub-target - however the status quo in specs naming is the opposite way round. ( I do not wish add further confusion here - but attempting to clarify - these styles of provision might not be suitable for the specific case, I guess - anyway, at this point, I’ve got nothing more to add :) ) Iain > >> But doesn't somehow this whole thing feel a bit like "chating the >> system"? ;-) >> Can't you actually achieve your thing (TLS model) via (new) 'EXTRA_SPECS' >> in 'gcc/config/rtems.h', for example? > > The EXTRA_SPECS definition seems to be target-specific. Not all targets let an operating system define SUBTARGET_EXTRA_SPECS. The SUBTARGET_EXTRA_SPECS would need to get propagated to the corresponding specs, which seems to be also target-specific, for example for mips we have: > > #undef CC1_SPEC > #define CC1_SPEC "\ > %{G*} %{EB:-meb} %{EL:-mel} %{EB:%{EL:%emay not use both -EB and -EL}} \ > %(subtarget_cc1_spec)" > > I think going this route would lead to a lot of changes affecting all targets. > > -- > embedded brains GmbH > Herr Sebastian HUBER > Dornierstr. 4 > 82178 Puchheim > Germany > email: sebastian.huber@embedded-brains.de > phone: +49-89-18 94 741 - 16 > fax: +49-89-18 94 741 - 08 > > Registergericht: Amtsgericht München > Registernummer: HRB 157899 > Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler > Unsere Datenschutzerklärung finden Sie hier: > https://embedded-brains.de/datenschutzerklaerung/
Sebastian Huber <sebastian.huber@embedded-brains.de> writes: > On 06.12.22 22:06, Thomas Schwinge wrote: >> Hi! >> >> I suppose I just fail to see some detail here, but: >> >> On 2022-11-21T08:25:25+0100, Sebastian Huber<sebastian.huber@embedded-brains.de> wrote: >>> gcc/ChangeLog: >>> >>> * gcc.cc (SUBTARGET_CC1_SPEC): Define if not defined. >>> (cc1_spec): Append SUBTARGET_CC1_SPEC. >>> --- >>> v2: Append SUBTARGET_CC1_SPEC directly to cc1_spec and not through CC1_SPEC. >>> This avoids having to modify all the CC1_SPEC definitions in the targets. >>> >>> gcc/gcc.cc | 9 ++++++++- >>> 1 file changed, 8 insertions(+), 1 deletion(-) >>> >>> diff --git a/gcc/gcc.cc b/gcc/gcc.cc >>> index 830ab88701f..4e1574a4df1 100644 >>> --- a/gcc/gcc.cc >>> +++ b/gcc/gcc.cc >>> @@ -706,6 +706,13 @@ proper position among the other output files. */ >>> #define CPP_SPEC "" >>> #endif >>> >>> +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and >>> + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended >>> + to CC1_SPEC. */ >>> +#ifndef SUBTARGET_CC1_SPEC >>> +#define SUBTARGET_CC1_SPEC "" >>> +#endif >>> + >>> /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus >>> or extra switch-translations. */ >>> #ifndef CC1_SPEC >>> @@ -1174,7 +1181,7 @@ proper position among the other output files. */ >>> static const char *asm_debug = ASM_DEBUG_SPEC; >>> static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; >>> static const char *cpp_spec = CPP_SPEC; >>> -static const char *cc1_spec = CC1_SPEC; >>> +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; >>> static const char *cc1plus_spec = CC1PLUS_SPEC; >>> static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; >>> static const char *link_ssp_spec = LINK_SSP_SPEC; >> ... doesn't this (at least potentially?) badly interact with any existing >> 'SUBTARGET_CC1_SPEC' definitions -- which pe rabove get appended to >> 'cc1_spec'? >> >> gcc/config/loongarch/gnu-user.h- and provides this hook instead. */ >> gcc/config/loongarch/gnu-user.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/loongarch/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >> gcc/config/loongarch/gnu-user.h- >> -- >> gcc/config/loongarch/loongarch.h-#define EXTRA_SPECS \ >> gcc/config/loongarch/loongarch.h: {"subtarget_cc1_spec", SUBTARGET_CC1_SPEC}, \ >> gcc/config/loongarch/loongarch.h- {"subtarget_cpp_spec", SUBTARGET_CPP_SPEC}, \ >> -- >> gcc/config/mips/gnu-user.h- and provides this hook instead. */ >> gcc/config/mips/gnu-user.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/mips/gnu-user.h:#define SUBTARGET_CC1_SPEC GNU_USER_TARGET_CC1_SPEC >> gcc/config/mips/gnu-user.h- >> -- >> gcc/config/mips/linux-common.h- >> gcc/config/mips/linux-common.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/mips/linux-common.h:#define SUBTARGET_CC1_SPEC \ >> gcc/config/mips/linux-common.h- LINUX_OR_ANDROID_CC (GNU_USER_TARGET_CC1_SPEC, \ >> -- >> gcc/config/mips/mips.h- >> gcc/config/mips/mips.h:/* SUBTARGET_CC1_SPEC is passed to the compiler proper. It may be >> gcc/config/mips/mips.h- overridden by subtargets. */ >> gcc/config/mips/mips.h:#ifndef SUBTARGET_CC1_SPEC >> gcc/config/mips/mips.h:#define SUBTARGET_CC1_SPEC "" >> gcc/config/mips/mips.h-#endif >> -- >> gcc/config/mips/mips.h-#define EXTRA_SPECS \ >> gcc/config/mips/mips.h: { "subtarget_cc1_spec", SUBTARGET_CC1_SPEC }, \ >> gcc/config/mips/mips.h- { "subtarget_cpp_spec", SUBTARGET_CPP_SPEC }, \ >> -- >> gcc/config/mips/r3900.h-/* By default (if not mips-something-else) produce code for the r3900 */ >> gcc/config/mips/r3900.h:#undef SUBTARGET_CC1_SPEC >> gcc/config/mips/r3900.h:#define SUBTARGET_CC1_SPEC "\ >> gcc/config/mips/r3900.h-%{mhard-float:%e-mhard-float not supported} \ > > Oh, I came up with the name SUBTARGET_CC1_SPEC after a discussion on the > mailing list and I have to admit that I didn't check that it was > actually already in use. What about renaming the loongarch/mips define > to LOONGARCH_CC1_SPEC and MIPS_CC1_SPEC? One drawback to that is that people might have their own spec files that reference the existing names. Typically those would be produced by using -dumpspecs and editing the output. I think we only really support that if people regenerate the specs files for each release, but for targets like MIPS that don't see much activity, it's probably easy to get away without doing that. How about going back to Jose's suggestion from the original thread of using OS_CC1_SPEC? The patch is OK with that change if no-one objects in 24 hours. Thanks, Richard
On 07/12/2022 10:50, Richard Sandiford wrote: > How about going back to Jose's suggestion from the original thread > of using OS_CC1_SPEC? The patch is OK with that change if no-one > objects in 24 hours. I checked in this change: https://gcc.gnu.org/git/?p=gcc.git;a=commit;h=3e4b8dc477c12f303171ec7f0394c97494095545
diff --git a/gcc/gcc.cc b/gcc/gcc.cc index 830ab88701f..4e1574a4df1 100644 --- a/gcc/gcc.cc +++ b/gcc/gcc.cc @@ -706,6 +706,13 @@ proper position among the other output files. */ #define CPP_SPEC "" #endif +/* Subtargets can define SUBTARGET_CC1_SPEC to provide extra args to cc1 and + cc1plus or extra switch-translations. The SUBTARGET_CC1_SPEC is appended + to CC1_SPEC. */ +#ifndef SUBTARGET_CC1_SPEC +#define SUBTARGET_CC1_SPEC "" +#endif + /* config.h can define CC1_SPEC to provide extra args to cc1 and cc1plus or extra switch-translations. */ #ifndef CC1_SPEC @@ -1174,7 +1181,7 @@ proper position among the other output files. */ static const char *asm_debug = ASM_DEBUG_SPEC; static const char *asm_debug_option = ASM_DEBUG_OPTION_SPEC; static const char *cpp_spec = CPP_SPEC; -static const char *cc1_spec = CC1_SPEC; +static const char *cc1_spec = CC1_SPEC SUBTARGET_CC1_SPEC; static const char *cc1plus_spec = CC1PLUS_SPEC; static const char *link_gcc_c_sequence_spec = LINK_GCC_C_SEQUENCE_SPEC; static const char *link_ssp_spec = LINK_SSP_SPEC;