public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc(refs/users/aoliva/heads/testme)] Fix testsuite/g++.dg/opt/20050511-1.C compilation error on VxWorks 7
Date: Fri, 25 Dec 2020 01:46:39 +0000 (GMT)	[thread overview]
Message-ID: <20201225014639.D07743854801@sourceware.org> (raw)

https://gcc.gnu.org/g:bf43ee3d9efbbcd1d708d39057547ff054678b3c

commit bf43ee3d9efbbcd1d708d39057547ff054678b3c
Author: Jerome Lambourg <lambourg@adacore.com>
Date:   Thu Dec 24 22:43:26 2020 -0300

    Fix testsuite/g++.dg/opt/20050511-1.C compilation error on VxWorks 7
    
    In VxWorks 7, UINT32 is defined in both modes, kernel and rtp.  Adjust
    the work around accordingly.
    
    
    for  gcc/testsuite/ChangeLog
    
            * g++.dg/opt/20050511-1.C: Work around UINT32 in vxworks rtp
            headers too.

Diff:
---
 gcc/testsuite/g++.dg/opt/20050511-1.C | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/gcc/testsuite/g++.dg/opt/20050511-1.C b/gcc/testsuite/g++.dg/opt/20050511-1.C
index a840fb0db8e..7041a482001 100644
--- a/gcc/testsuite/g++.dg/opt/20050511-1.C
+++ b/gcc/testsuite/g++.dg/opt/20050511-1.C
@@ -5,7 +5,7 @@
 #include <stdlib.h>
 
 // The VxWorks kernel headers define their own UINT32
-#if defined __vxworks && !defined __RTP__
+#if defined __vxworks
 #define UINT32 my_UINT32
 #endif


             reply	other threads:[~2020-12-25  1:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-25  1:46 Alexandre Oliva [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-01-01  1:30 Alexandre Oliva
2020-12-18 14:47 Alexandre Oliva

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=20201225014639.D07743854801@sourceware.org \
    --to=aoliva@gcc.gnu.org \
    --cc=gcc-cvs@gcc.gnu.org \
    /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).