From: Segher Boessenkool <segher@kernel.crashing.org>
To: Olivier Hainque <hainque@adacore.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Rasmus Villemoes <rv@rasmusvillemoes.dk>
Subject: Re: [patch] Rework CPP_BUILTINS_SPEC for powerpc-vxworks
Date: Tue, 13 Oct 2020 10:38:30 -0500 [thread overview]
Message-ID: <20201013153830.GW2672@gate.crashing.org> (raw)
In-Reply-To: <F52EFDF7-9BC0-4F7A-8D94-956966A8A417@adacore.com>
Hi!
On Tue, Oct 13, 2020 at 03:35:11PM +0200, Olivier Hainque wrote:
> Here's an updated version which passed in-house build & tests
> with gcc-10 based toolchains for VxWorks 6.9 & 7.2, and with which
> I could build mainline for VxWorks 6.9 including libstdc++ (combined
> with a few other patches, orthogonal to what is proposed here and
> which I'll post shortly).
>
> Same ChangeLog. Patch hopefully quotable if needed now.
It is, thank you!
The patch looks fine to me now. Not that you need my approval :-)
Segher
next prev parent reply other threads:[~2020-10-13 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-01 9:30 Olivier Hainque
2020-10-02 22:43 ` Segher Boessenkool
2020-10-05 17:27 ` Olivier Hainque
2020-10-13 13:35 ` Olivier Hainque
2020-10-13 15:38 ` Segher Boessenkool [this message]
2020-10-14 10:52 ` Olivier Hainque
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=20201013153830.GW2672@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=hainque@adacore.com \
--cc=rv@rasmusvillemoes.dk \
/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).