From: Uros Bizjak <ubizjak@gmail.com>
To: GCC <gcc@gcc.gnu.org>, David Edelsohn <dje@watson.ibm.com>,
Andrew Pinski <pinskia@gmail.com>
Subject: rs6000, SPU: vcond pattern can not FAIL
Date: Thu, 13 Aug 2009 21:52:00 -0000 [thread overview]
Message-ID: <4A84399F.5010207@gmail.com> (raw)
Hello!
I would like to warn rs6000 and SPU maintainers, that vcond patterns can
_not_ FAIL. Please see PR41019 [1] for the proposed fix for x86. The
same problem can be triggered on rs6000 and SPU, it can happen that the
vcond pattern is only partially expanded.
The problem is, that middle end checks only for the existence of the
pattern, not if it can FAIL.
BTW: The documentation says:
--cut here--
`FAIL'
Make the pattern fail on this occasion. When a pattern fails, it
means that the pattern was not truly available. The calling
routines in the compiler will try other strategies for code
generation using other patterns.
Failure is currently supported only for binary (addition,
multiplication, shifting, etc.) and bit-field (`extv', `extzv',
and `insv') operations.
...
--cut here--
[1] http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41019
Uros.
reply other threads:[~2009-08-13 16:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4A84399F.5010207@gmail.com \
--to=ubizjak@gmail.com \
--cc=dje@watson.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=pinskia@gmail.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).