From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: "Jose E. Marchesi" <jose.marchesi@oracle.com>
Cc: gcc-patches@gcc.gnu.org, Iain Sandoe <idsandoe@googlemail.com>
Subject: Re: [PATCH 1/2] Allow subtarget customization of CC1_SPEC
Date: Mon, 25 Jul 2022 07:59:42 +0200 [thread overview]
Message-ID: <b0a886e8-cf72-ed0d-5d8e-4804ce48c0f4@embedded-brains.de> (raw)
In-Reply-To: <87bkth454k.fsf@oracle.com>
Hallo Jose,
On 22/07/2022 16:02, Jose E. Marchesi wrote:
> I find "subtarget" confusing in this context.
>
> If it is about rtems.h, linux.h or sol2.h, wouldn't this be better
> called OS_CC1_SPEC or similar? These files specify configurations that
> apply to a set of targets, not to a subset of a target...
Iain Sandoe told me that for the GCC implementation the OSs are
sub-targets of the architecture:
https://gcc.gnu.org/pipermail/gcc/2022-July/239158.html
--
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/
next prev parent reply other threads:[~2022-07-25 5:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-22 13:02 Sebastian Huber
2022-07-22 13:02 ` [PATCH 2/2] RTEMS: Use local-exec TLS model by default Sebastian Huber
2022-07-22 14:02 ` [PATCH 1/2] Allow subtarget customization of CC1_SPEC Jose E. Marchesi
2022-07-25 5:59 ` Sebastian Huber [this message]
2022-07-25 6:06 ` Iain Sandoe
2022-08-04 13:02 ` Sebastian Huber
2022-09-08 5:33 ` Sebastian Huber
2022-10-04 9:47 ` Sebastian Huber
2022-10-26 9:34 ` Sebastian Huber
2022-11-20 16:57 ` Jeff Law
2022-11-21 7:26 ` Sebastian Huber
2022-11-21 14:58 ` Jeff Law
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=b0a886e8-cf72-ed0d-5d8e-4804ce48c0f4@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=idsandoe@googlemail.com \
--cc=jose.marchesi@oracle.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).