From: "Paulo Matos" <pmatos@broadcom.com>
To: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: DONT_BREAK_DEPENDENCIES bitmask for scheduling
Date: Mon, 01 Jul 2013 16:31:00 -0000 [thread overview]
Message-ID: <19EB96622A777C4AB91610E763265F46231E97@SJEXCHMB14.corp.ad.broadcom.com> (raw)
Hi,
Near the start of schedule_block, find_modifiable_mems is called if DONT_BREAK_DEPENDENCIES is not enabled for this scheduling pass. It seems on c6x backend currently uses this.
However, it's quite strange that this is not a requirement for all backends since find_modifiable_mems, moves all my dependencies in SD_LIST_HARD_BACK to SD_LIST_SPEC_BACK even though I don't have DO_SPECULATION enabled.
Since dependencies are accessed later on from try_ready (for example), I would have thought that it would be always good not to call find_modifiable_mems, given that it seems to 'literally' break dependencies.
Is the behaviour of find_modifiable_mems a bug or somehow expected?
Cheers,
Paulo Matos
next reply other threads:[~2013-07-01 16:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-01 16:31 Paulo Matos [this message]
2013-12-10 16:18 ` Ramana Radhakrishnan
2013-12-10 21:44 ` Maxim Kuvyrkov
2013-12-10 22:14 ` Ramana Radhakrishnan
2013-12-11 0:03 ` Maxim Kuvyrkov
2013-12-11 2:45 ` Ramana Radhakrishnan
2013-12-11 2:56 ` Maxim Kuvyrkov
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=19EB96622A777C4AB91610E763265F46231E97@SJEXCHMB14.corp.ad.broadcom.com \
--to=pmatos@broadcom.com \
--cc=gcc@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).