From: Christophe Lyon <christophe.lyon@linaro.org>
To: sellcey@cavium.com
Cc: Alexander Monakov <amonakov@ispras.ru>,
Andrew Pinski <pinskia@gmail.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: Re: [reviewed] qsort comparator consistency checking
Date: Fri, 29 Sep 2017 19:43:00 -0000 [thread overview]
Message-ID: <CAKdteOZdx9GNXO1RBZM8WYSchg=u+UvVA7BPs2SLVi9JHVP_pQ@mail.gmail.com> (raw)
In-Reply-To: <1506713976.15649.35.camel@cavium.com>
On 29 September 2017 at 21:39, Steve Ellcey <sellcey@cavium.com> wrote:
> On Fri, 2017-09-29 at 21:14 +0300, Alexander Monakov wrote:
>> On Fri, 29 Sep 2017, Andrew Pinski wrote:
>> >
>> > >
>> > > This patch (r253295) breaks the gcc build for aarch64-linux-gnu:
>> > I was just about to report the same thing.
>> I think autoprefetch ranking heuristic is still wrong if
>> multi_mem_insn_p
>> may be true; please try this patch.
>>
>> * haifa-sched.c (autopref_rank_data): Remove.
>> (autopref_rank_for_schedule): Only use min_offset difference.
>
> This fixed the build for me on aarch64. I am still running the
> testsuite.
>
It doesn't for me. I'm getting another build error:
/home/christophe.lyon/src/GCC/sources/gcc-fsf/aarch64-build/gcc/haifa-sched.c:
In function ‘int autopref_multipass_dfa_lookahead_guard_1(const
rtx_insn*, const rtx_insn*, int)’:
/home/christophe.lyon/src/GCC/sources/gcc-fsf/aarch64-build/gcc/haifa-sched.c:5700:42:
error: ‘autopref_rank_data’ was not declared in this scope
The removed autopref_rank_data function is still called by
autopref_multipass_dfa_lookahead_guard_1.
Christophe
> Steve Ellcey
> sellcey@cavium.com
next prev parent reply other threads:[~2017-09-29 19:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 13:29 Alexander Monakov
2017-09-29 17:46 ` Christophe Lyon
2017-09-29 17:58 ` Andrew Pinski
2017-09-29 18:14 ` Alexander Monakov
2017-09-29 19:39 ` Steve Ellcey
2017-09-29 19:43 ` Christophe Lyon [this message]
2017-09-29 19:46 ` Steve Ellcey
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='CAKdteOZdx9GNXO1RBZM8WYSchg=u+UvVA7BPs2SLVi9JHVP_pQ@mail.gmail.com' \
--to=christophe.lyon@linaro.org \
--cc=amonakov@ispras.ru \
--cc=gcc-patches@gcc.gnu.org \
--cc=pinskia@gmail.com \
--cc=sellcey@cavium.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).