From: Segher Boessenkool <segher@kernel.crashing.org>
To: Carl Love <cel@us.ibm.com>
Cc: gcc-patches@gcc.gnu.org, David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH rs6000] Fix for builtins-4-runnable.c testcase FAIL on power7/BE 32-bit
Date: Fri, 09 Feb 2018 23:13:00 -0000 [thread overview]
Message-ID: <20180209231333.GX21977@gate.crashing.org> (raw)
In-Reply-To: <1518193377.7508.2.camel@us.ibm.com>
Hi Carl,
On Fri, Feb 09, 2018 at 08:22:57AM -0800, Carl Love wrote:
> The following patch contains fixes for the builtins4-runnable.c test in
> 32-bit mode for the current GCC 8 branch. This is issue #290 in Bill
> Schmidt's issues. The int128 and uint128 variable types are not
> supported in 32-bit mode. The tests were moved to a new test file and
> restricted to run only when int128 type is supported.
> 2018-02-09  Carl Love  <cel@us.ibm.com>
>
> * gcc.target/powerpc/builtins-4-runnable.c (main): Move
> int128 and
> uint128 tests to new testfile.
> * gcc.target/powerpc/builtins-4-int128-runnable.c: New testfile
> for
> int128 and uint128 tests.
> * gcc.target/powerpc/powerpc.exp: Add builtins-4-int128-
> runnable.c to
> list oftorture tests.
Missing space (and the layout is messed up a bit, that's your mailer
I guess -- the patch is wrapped as well, that's not good).
Okay for trunk. Thanks!
Segher
prev parent reply other threads:[~2018-02-09 23:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 16:23 Carl Love
2018-02-09 22:09 ` Carl Love
2018-02-12 15:17 ` Segher Boessenkool
2018-02-12 16:20 ` Carl Love
2018-02-12 16:51 ` Segher Boessenkool
2018-02-09 23:13 ` Segher Boessenkool [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=20180209231333.GX21977@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=cel@us.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=wschmidt@linux.vnet.ibm.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).