From: Segher Boessenkool <segher@kernel.crashing.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Bill Schmidt <wschmidt@linux.vnet.ibm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>,
jakub@redhat.com, David Edelsohn <dje.gcc@gmail.com>
Subject: Re: [PATCH, rs6000] Clean up capitalized diagnostic messages
Date: Mon, 07 Aug 2017 10:51:00 -0000 [thread overview]
Message-ID: <20170807105045.GE13471@gate.crashing.org> (raw)
In-Reply-To: <8760e1dsp4.fsf@linux-m68k.org>
Hi Andreas,
On Sun, Aug 06, 2017 at 10:08:23AM +0200, Andreas Schwab wrote:
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for errors, line 18)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for errors, line 18)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-exp-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c (test for errors, line 16)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c (test for errors, line 16)
> FAIL: gcc.target/powerpc/bfp/scalar-extract-sig-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-11.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-5.c (test for excess errors)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c (test for errors, line 20)
> FAIL: gcc.target/powerpc/bfp/scalar-insert-exp-8.c (test for excess errors)
> FAIL: gcc.target/powerpc/cmpb-3.c (test for errors, line 12)
> FAIL: gcc.target/powerpc/cmpb-3.c (test for excess errors)
> FAIL: gcc.target/powerpc/byte-in-set-2.c (test for errors, line 15)
> FAIL: gcc.target/powerpc/byte-in-set-2.c (test for excess errors)
> FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c (test for errors, line 17)
> FAIL: gcc.target/powerpc/vsu/vec-xl-len-13.c (test for excess errors)
> FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c (test for errors, line 18)
> FAIL: gcc.target/powerpc/vsu/vec-xst-len-13.c (test for excess errors)
What target? What configure options? What runtest options? What
binutils version? What is the actual CPU?
Or, do you have a link to a gcc-testresults post with that info?
Segher
next prev parent reply other threads:[~2017-08-07 10:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-02 15:29 Bill Schmidt
2017-08-02 15:55 ` Jakub Jelinek
2017-08-02 16:04 ` Joseph Myers
2017-08-02 18:50 ` Bill Schmidt
2017-08-02 16:49 ` Martin Sebor
2017-08-02 23:44 ` Segher Boessenkool
2017-08-03 18:28 ` Bill Schmidt
2017-08-06 8:08 ` Andreas Schwab
2017-08-07 10:51 ` Segher Boessenkool [this message]
2017-08-08 12:46 ` Bill Schmidt
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=20170807105045.GE13471@gate.crashing.org \
--to=segher@kernel.crashing.org \
--cc=dje.gcc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=schwab@linux-m68k.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).