public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "irar at il dot ibm dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/35642] [4.4 Regression] heisenbug in tree vectorizer Date: Sun, 06 Jul 2008 11:55:00 -0000 [thread overview] Message-ID: <20080706115427.2469.qmail@sourceware.org> (raw) In-Reply-To: <bug-35642-11013@http.gcc.gnu.org/bugzilla/> ------- Comment #14 from irar at il dot ibm dot com 2008-07-06 11:54 ------- All those failures occur because vector multiplication of shorts to shorts is not supported on power. Paolo's patch changed the order of type conversion and multiplication, and removed type conversions. All those loops contain multiplication either of type short = short * constant or short = int * constant. For the first case we used to have conversion to int, multiplication, and conversion to short, and now there are no type conversions. For the second case, before the patch there was first multiplication of ints and then the result was converted to short, and now the conversion to short comes first and then there is multiplication of shorts. In other words, before Paolo's patch those loops contained multiplications of ints (supported) and now they contain multiplications of shorts (not supported). As for the heisenbug, first of all, the failures occur with and without bootstrap. Also Victor tried to reproduced the behavior that Kenny described in comment #3 (on the same revision and the same configuration), but he saw the failures with a bootstrapped version too. I.e., we can't reproduce the random behavior - the failures are deterministic and well understood. I suggest to open a missed-optimization PR for vector multiplication of shorts to shorts (seems easy to fix), to xfail the tests, and to close this PR. Ira -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35642
next prev parent reply other threads:[~2008-07-06 11:55 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-03-19 18:42 [Bug tree-optimization/35642] New: " zadeck at naturalbridge dot com 2008-03-19 19:16 ` [Bug tree-optimization/35642] " pinskia at gcc dot gnu dot org 2008-03-19 19:18 ` pinskia at gcc dot gnu dot org 2008-03-19 19:26 ` zadeck at naturalbridge dot com 2008-03-20 9:31 ` irar at il dot ibm dot com 2008-03-20 9:43 ` victork at gcc dot gnu dot org 2008-03-20 13:44 ` victork at gcc dot gnu dot org 2008-03-20 13:52 ` bonzini at gnu dot org 2008-03-20 14:00 ` zadeck at naturalbridge dot com 2008-03-20 14:08 ` bonzini at gnu dot org 2008-04-07 1:59 ` [Bug tree-optimization/35642] [4.4 Regression] " pinskia at gcc dot gnu dot org 2008-04-20 20:40 ` rguenth at gcc dot gnu dot org 2008-04-20 21:22 ` zadeck at naturalbridge dot com 2008-04-20 21:54 ` rguenth at gcc dot gnu dot org 2008-05-22 5:42 ` irar at il dot ibm dot com 2008-07-06 11:55 ` irar at il dot ibm dot com [this message] 2008-07-06 11:56 ` irar at il dot ibm dot com 2008-07-06 11:58 ` irar at il dot ibm dot com 2008-07-10 14:06 ` [Bug tree-optimization/35642] [4.4 Regression] short * short multiplication not vectorized on Power bonzini at gnu dot org 2008-07-13 6:01 ` irar at il dot ibm dot com 2008-07-18 16:49 ` rguenth at gcc dot gnu dot org 2008-09-07 8:56 ` irar at gcc dot gnu dot org 2008-09-07 11:07 ` irar at il dot ibm dot com
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=20080706115427.2469.qmail@sourceware.org \ --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: linkBe 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).