From: Richard Henderson <rth@redhat.com>
To: Bingfeng Mei <bmei@broadcom.com>
Cc: "gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Can GCC scheduler take advantage of mutually exclusive predicated blocks?
Date: Tue, 07 Jul 2009 16:28:00 -0000 [thread overview]
Message-ID: <4A5377AD.8010503@redhat.com> (raw)
In-Reply-To: <7FB04A5C213E9943A72EE127DB74F0AD93C58A1C3B@SJEXCHCCR02.corp.ad.broadcom.com>
On 07/07/2009 02:21 AM, Bingfeng Mei wrote:
> Hello,
> Our GCC port& VLIW target processor support predication. However, I don't
> see the GCC schedule two mutually exclusive blocks (from IF and ELSE ) in
> a way that they are independent from each other.
>
> I am wondering if this is a problem of our porting and I missed some tricks
> , or it is current limitation of GCC.
It can, but the test is fairly weak. See conditions_mutex_p in
sched-deps.c. This could probably be enhanced...
r~
prev parent reply other threads:[~2009-07-07 16:28 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-07 9:22 Bingfeng Mei
2009-07-07 16:28 ` Richard Henderson [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=4A5377AD.8010503@redhat.com \
--to=rth@redhat.com \
--cc=bmei@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).