From: Uros Bizjak <ubizjak@gmail.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Cc: Mike Stump <mikestump@comcast.net>
Subject: Re: [PATCH] g++.dg/init/vbase1.C and g++.dg/cpp/ucn-1.C
Date: Sat, 21 Nov 2015 12:34:00 -0000 [thread overview]
Message-ID: <CAFULd4bmC-cxHcKHav9drWJzZqkuRhG0d4wATjnaRupmS_uNSg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 438 bytes --]
> I fixed this with the below patch. Tested on x86_64 linux, x86_64 darwin and my port. If you want to
> list aarch64/arn and mips, please do.
>
> * g++.dg/init/vbase1.C: Only run on x86_64-*-* as this testcase
> isn't portable.
I have added i?86-*-* to the list.
2015-11-21 Uros Bizjak <ubizjak@gmail.com>
* g++.dg/init/vbase1.C: Also run on i?86-*-*.
Tested on x86_64-linux-gnu {,-m32} and committed to mainline SVN.
Uros.
[-- Attachment #2: t.diff.txt --]
[-- Type: text/plain, Size: 628 bytes --]
Index: g++.dg/init/vbase1.C
===================================================================
--- g++.dg/init/vbase1.C (revision 230701)
+++ g++.dg/init/vbase1.C (working copy)
@@ -42,4 +42,4 @@
// Verify that the SubB() mem-initializer is storing 0 directly into
// this->D.whatever rather than into a stack temp that is then copied into the
// base field.
-// { dg-final { scan-rtl-dump "set \[^\n\]*\n\[^\n\]*this\[^\n\]*\n\[^\n\]*const_int 0" "expand" { target { x86_64-*-* } } } }
+// { dg-final { scan-rtl-dump "set \[^\n\]*\n\[^\n\]*this\[^\n\]*\n\[^\n\]*const_int 0" "expand" { target { i?86-*-* x86_64-*-* } } } }
next reply other threads:[~2015-11-21 12:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-21 12:34 Uros Bizjak [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-14 0:33 David Edelsohn
2015-11-14 1:01 ` Mike Stump
2015-11-14 10:16 ` Andreas Schwab
2015-11-14 13:09 ` David Edelsohn
2015-11-14 13:31 ` Jakub Jelinek
2015-11-14 13:36 ` David Edelsohn
2015-11-14 13:42 ` Andreas Schwab
2015-11-14 13:47 ` David Edelsohn
2015-11-16 9:15 ` Eric Botcazou
2015-11-16 13:29 ` David Edelsohn
2015-11-16 14:02 ` Renlin Li
2015-11-20 22:17 ` Mike Stump
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=CAFULd4bmC-cxHcKHav9drWJzZqkuRhG0d4wATjnaRupmS_uNSg@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mikestump@comcast.net \
/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).