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)] gcc.dg/intmax_t-1.c compiles without error on VxWorks 7 SR06x0 Date: Fri, 1 Jan 2021 01:29:31 +0000 (GMT) [thread overview] Message-ID: <20210101012931.38F203857815@sourceware.org> (raw) https://gcc.gnu.org/g:7620fcde46c481e525dd822603772685f52f0d44 commit 7620fcde46c481e525dd822603772685f52f0d44 Author: Joel Brobecker <brobecker@adacore.com> Date: Thu Dec 31 21:37:45 2020 -0300 gcc.dg/intmax_t-1.c compiles without error on VxWorks 7 SR06x0 This test currently fails on VxWorks 7 SR06x0 targets when in kernel mode, because it expects a discrepancy between built-in and system intmax_t for all VxWorks targets when in kernel mode. Fortunately, this has now been fixed when targetting VxWorks 7 SR06x0, so this commit adjusts the "dg-error" condition to exclude newer versions of VxWorks 7. for gcc/testsuite/ChangeLog * gcc.dg/intmax_t-1.c: Do not expect an error on *-*-vxworks7r* targets. Diff: --- gcc/testsuite/gcc.dg/intmax_t-1.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/testsuite/gcc.dg/intmax_t-1.c b/gcc/testsuite/gcc.dg/intmax_t-1.c index 00b503c2509..03d4266cc7b 100644 --- a/gcc/testsuite/gcc.dg/intmax_t-1.c +++ b/gcc/testsuite/gcc.dg/intmax_t-1.c @@ -1,6 +1,6 @@ /* { dg-do compile } */ /* { dg-options "-Wall" } */ -/* { dg-error "" "" { target { { *arm*-*-*elf* xtensa*-*-elf* } || vxworks_kernel } } 0 } */ +/* { dg-error "" "" { target { { *arm*-*-*elf* xtensa*-*-elf* } || { vxworks_kernel && { ! *-*-vxworks7r* } } } } 0 } */ /* Compile with -Wall to get a warning if built-in and system intmax_t don't match. */
next reply other threads:[~2021-01-01 1:29 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-01-01 1:29 Alexandre Oliva [this message] -- strict thread matches above, loose matches on Subject: below -- 2020-12-25 1:45 Alexandre Oliva 2020-12-18 14:46 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=20210101012931.38F203857815@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: linkBe 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).