From: Siddhesh Poyarekar <siddhesh@gotplt.org>
To: Martin Sebor <msebor@gmail.com>,
Gcc Patch List <gcc-patches@gcc.gnu.org>,
Jakub Jelinek <jakub@redhat.com>
Subject: Re: [PATCH] correct -Wrestrict handling of arrays of arrays (PR 84095)
Date: Fri, 23 Feb 2018 16:19:00 -0000 [thread overview]
Message-ID: <05af4357-1bec-477d-e6bb-1827706b9b93@gotplt.org> (raw)
In-Reply-To: <ed293e7f-a4b7-1dc0-0f16-b3f5599dd98d@gmail.com>
On Friday 23 February 2018 09:22 PM, Martin Sebor wrote:
> I see no failures in this test in any of the recently reported
> results on any targets except those below:
>
> https://gcc.gnu.org/ml/gcc-testresults/2018-02/msg01530.html
> https://gcc.gnu.org/ml/gcc-testresults/2018-02/msg01514.html
>
> There are a large number of failures in these reports in many
> tests that were reported previously (before r257910), suggesting
> something else is wrong. They all seem to use -fpic.
>
> If you referring to some other report or your own result please
> post a link or say what target/configuration, etc..
This was on my x86_64 box (Xeon(R) CPU E5-2623) and a standard
x86_64-pc-linux-gnu native build. It was after an incremental build
though, so I'll schedule a fresh one next week to confirm if you think
that shouldn't happen.
Siddhesh
next prev parent reply other threads:[~2018-02-23 16:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 23:37 Martin Sebor
2018-02-01 23:45 ` Martin Sebor
2018-02-09 2:46 ` Martin Sebor
2018-02-14 6:14 ` Jeff Law
2018-02-15 17:48 ` Martin Sebor
2018-02-16 23:39 ` Jeff Law
2018-02-23 3:17 ` Siddhesh Poyarekar
2018-02-23 15:52 ` Martin Sebor
2018-02-23 16:19 ` Siddhesh Poyarekar [this message]
2018-02-23 16:49 ` Jakub Jelinek
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=05af4357-1bec-477d-e6bb-1827706b9b93@gotplt.org \
--to=siddhesh@gotplt.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=msebor@gmail.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).