public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/26128] Trivial operation not vectorized on char Date: Mon, 06 Feb 2006 15:00:00 -0000 [thread overview] Message-ID: <20060206150037.25776.qmail@sourceware.org> (raw) In-Reply-To: <bug-26128-10506@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from pinskia at gcc dot gnu dot org 2006-02-06 15:00 ------- Actually this is a known regression and a missed optimization regression caused by fixing up wrong code. The work around is to use -fwrapv. -- pinskia at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Severity|normal |enhancement Status|UNCONFIRMED |NEW Component|regression |tree-optimization Ever Confirmed|0 |1 Keywords| |missed-optimization Last reconfirmed|0000-00-00 00:00:00 |2006-02-06 15:00:36 date| | Summary|Regression vs |Trivial operation not |4.1.0cvs20051015 - Trivial |vectorized on char |operation not vectorized | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26128
next prev parent reply other threads:[~2006-02-06 15:00 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-06 14:55 [Bug regression/26128] New: Regression vs 4.1.0cvs20051015 - Trivial operation not vectorized hurbain at cri dot ensmp dot fr 2006-02-06 15:00 ` pinskia at gcc dot gnu dot org [this message] 2006-09-21 17:12 ` [Bug tree-optimization/26128] Trivial operation not vectorized on char pinskia at gcc dot gnu dot org 2007-06-12 17:37 ` [Bug tree-optimization/26128] Trivial operation not vectorized on char/short pinskia at gcc dot gnu dot org 2009-02-06 1:45 ` pinskia at gcc dot gnu dot 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=20060206150037.25776.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).