From: Peter Bergner <bergner@vnet.ibm.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Segher Boessenkool <segher@kernel.crashing.org>,
GCC Patches <gcc-patches@gcc.gnu.org>,
David Edelsohn <dje.gcc@gmail.com>,
Bill Schmidt <wschmidt@linux.vnet.ibm.com>
Subject: Re: [PATCH, rs6000] Fix PR target/80246, DFP builtins using the wrong types
Date: Sun, 02 Apr 2017 14:48:00 -0000 [thread overview]
Message-ID: <d22e7843-8df2-45d7-91d0-7f5ab5e1928d@vnet.ibm.com> (raw)
In-Reply-To: <87o9wfz2rc.fsf@linux-m68k.org>
On 4/2/17 2:29 AM, Andreas Schwab wrote:
>> +/* { dg-require-effective-target dfp } */
[snip]
> FAIL: gcc.target/powerpc/pr80246.c (test for excess errors)
> Excess errors:
> /daten/gcc/gcc-20170401/gcc/testsuite/gcc.target/powerpc/pr80246.c:18:10:
> error: Builtin function __builtin_dxex requires the -mhard-dfp option
What configure options are you using? I would have expected this the
dg-require-effective-target to disable this test if you don't have
-mhard-dfp.
Peter
next prev parent reply other threads:[~2017-04-02 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-29 21:20 Peter Bergner
2017-03-29 22:36 ` Segher Boessenkool
2017-03-30 7:33 ` Peter Bergner
2017-03-30 16:21 ` Peter Bergner
2017-04-02 7:21 ` Andreas Schwab
2017-04-02 7:29 ` Andreas Schwab
2017-04-02 14:48 ` Peter Bergner [this message]
2017-04-02 15:07 ` Andreas Schwab
2017-04-02 18:54 ` Segher Boessenkool
2017-04-03 14:41 ` Peter Bergner
2017-04-03 14:55 ` Peter Bergner
2017-04-03 16:04 ` Peter Bergner
2017-04-03 17:01 ` Peter Bergner
2017-04-03 18:08 ` Peter Bergner
2017-03-30 17:45 ` Segher Boessenkool
2017-03-30 18:27 ` Peter Bergner
2017-03-30 20:24 ` Peter Bergner
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=d22e7843-8df2-45d7-91d0-7f5ab5e1928d@vnet.ibm.com \
--to=bergner@vnet.ibm.com \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=segher@kernel.crashing.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).