public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/55155] Autovectorization does not use unaligned loads/stores Date: Wed, 31 Oct 2012 21:44:00 -0000 [thread overview] Message-ID: <bug-55155-4-wprtf2T1N6@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55155-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55155 --- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-10-31 21:44:20 UTC --- <bb 2>: _19 = num_prods_6(D) * 16; if (_19 != 0) goto <bb 4>; else goto <bb 3>; <bb 3>: return; <bb 4>: _16 = ASSERT_EXPR <_19, _19 != 0>; ... if (_16 <= 4) goto <bb 5>; else goto <bb 21>; We should have an assert_expr that _16 is also greater or equal to than 16. Note this is changing unsigned to __SIZE_TYPE__ so casting does not get in the way.
next prev parent reply other threads:[~2012-10-31 21:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-10-31 21:33 [Bug tree-optimization/55155] New: " sgunderson at bigfoot dot com 2012-10-31 21:44 ` pinskia at gcc dot gnu.org [this message] 2021-06-08 8:28 ` [Bug tree-optimization/55155] " pinskia at gcc dot gnu.org 2022-11-07 20:02 ` aldyh at gcc dot gnu.org
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-55155-4-wprtf2T1N6@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: 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).