public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "abel at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/60043] -fschedule-insns2 breaks anti-dependency
Date: Tue, 04 Feb 2014 09:37:00 -0000 [thread overview]
Message-ID: <bug-60043-4-J9eUEyDjR5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60043-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60043
--- Comment #5 from Andrey Belevantsev <abel at gcc dot gnu.org> ---
(In reply to Richard Biener from comment #4)
> Hmm, oops. The testcase has a true dependence ... ;) Still, isn't the
> code in sched_analyze_2 wrong? Or are pending_mems all before 't'?
Yes (to second question :). The analysis code roughly works like this
(sched_analyze is the entry point):
- process insns one by one in a bb/ebb doing two things in parallel:
o mark reads/writes to registers, writes/reads to mems of this insn in
various fields of the deps context; and
o find dependencies between this insn reads/writes of registers/memory and
previously noted reads/writes of the same register or memory from the deps
context.
So the pending_mem read/write will always happen before the currently
processing insn mem read/write.
prev parent reply other threads:[~2014-02-04 9:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 13:18 [Bug rtl-optimization/60043] New: " rguenth at gcc dot gnu.org
2014-02-04 6:59 ` [Bug rtl-optimization/60043] " abel at gcc dot gnu.org
2014-02-04 7:14 ` abel at gcc dot gnu.org
2014-02-04 9:26 ` rguenther at suse dot de
2014-02-04 9:27 ` rguenth at gcc dot gnu.org
2014-02-04 9:37 ` abel at gcc dot gnu.org [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=bug-60043-4-J9eUEyDjR5@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).