public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Alexandre Oliva <oliva@adacore.com>
Cc: gcc-patches@gcc.gnu.org, Jerome Lambourg <lambourg@adacore.com>
Subject: Re: Fix testsuite/g++.old-deja/g++.mike/p658.C build failure on VxWorks RTP
Date: Tue, 29 Dec 2020 10:48:40 -0800	[thread overview]
Message-ID: <A6D002B5-B8B1-452E-8A40-8A4DAFE4E6AE@comcast.net> (raw)
In-Reply-To: <orzh25frb2.fsf@lxoliva.fsfla.org>

On Dec 22, 2020, at 1:45 PM, Alexandre Oliva <oliva@adacore.com> wrote:
> 
> The conflicting definition of OK is present in VxWorks RTP headers too.
> 
> Regstrapped on x86_64-linux-gnu, and tested with -x-arm-wrs-vxworks7r2.
> Ok to install?

Ok.

Ok to stylize all the #undef in the same way.  This is one happens to use a slightly different stye then the others as I recall.

      reply	other threads:[~2020-12-29 18:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-22 21:45 Alexandre Oliva
2020-12-29 18:48 ` Mike Stump [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=A6D002B5-B8B1-452E-8A40-8A4DAFE4E6AE@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=lambourg@adacore.com \
    --cc=oliva@adacore.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).