From: Jakub Jelinek <jakub@redhat.com>
To: Christophe Lyon <christophe.lyon@linaro.org>
Cc: Jeff Law <law@redhat.com>,
Wilco Dijkstra <Wilco.Dijkstra@arm.com>,
gcc Patches <gcc-patches@gcc.gnu.org>, nd <nd@arm.com>
Subject: Re: [PATCH] Fix PR64242
Date: Tue, 04 Dec 2018 10:23:00 -0000 [thread overview]
Message-ID: <20181204102332.GH12380@tucnak> (raw)
In-Reply-To: <CAKdteOb2KWDfgLiPb9HYm14Jb=TizVBStwC2Am2j=yiAYuH1Ug@mail.gmail.com>
On Tue, Dec 04, 2018 at 11:20:38AM +0100, Christophe Lyon wrote:
> This commit didn't fix the failure I reported on some arm targets, and
> it introduced
> a regression on aarch64-none-elf with -mabi=ilp32:
> FAIL: gcc.c-torture/execute/pr64242.c -O0 execution test
> Il seems the test timed-out.
> Higher optimization levels still pass.
That just means the problem wasn't really fully fixed on those targets,
in the PR there are some comments about missing scheduling barriers.
Jakub
prev parent reply other threads:[~2018-12-04 10:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-29 19:26 Wilco Dijkstra
2018-11-30 23:07 ` Jeff Law
2018-12-03 13:34 ` Richard Biener
2018-12-03 13:40 ` Christophe Lyon
2018-12-03 16:26 ` Jakub Jelinek
2018-12-03 18:53 ` Jeff Law
2018-12-04 10:20 ` Christophe Lyon
2018-12-04 10:23 ` Jakub Jelinek [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=20181204102332.GH12380@tucnak \
--to=jakub@redhat.com \
--cc=Wilco.Dijkstra@arm.com \
--cc=christophe.lyon@linaro.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=law@redhat.com \
--cc=nd@arm.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).