public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/56157] [4.8 Regression] ICE with -ftree-vectorize in in compute_live_loop_exits Date: Thu, 31 Jan 2013 11:54:00 -0000 [thread overview] Message-ID: <bug-56157-4-5OuJzoreBB@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-56157-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56157 --- Comment #6 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-31 11:54:09 UTC --- Reduced testcase: struct Pixel { unsigned short r; unsigned short g; unsigned short b; unsigned short a; }; void fn(unsigned char *dst, const unsigned char *src, unsigned width) { unsigned x; for(x = 0; x < width; x += 1) { struct Pixel pixel; pixel.r = (unsigned short)(((unsigned)src[0]) * 0xffff / 0xff); pixel.g = (unsigned short)(((unsigned)src[1]) * 0xffff / 0xff); pixel.b = (unsigned short)(((unsigned)src[2]) * 0xffff / 0xff); pixel.a = (unsigned short)(((unsigned)src[3]) * 0xffff / 0xff); __builtin_memcpy(dst, &pixel, sizeof pixel); src += 4; dst += 8; } }
next prev parent reply other threads:[~2013-01-31 11:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-30 21:43 [Bug tree-optimization/56157] New: ICE with -ftree-vectorize in in compute_live_loop_exits (4.8 trunk) jana at saout dot de 2013-01-31 8:46 ` [Bug tree-optimization/56157] [4.8 Regression] ICE with -ftree-vectorize in in compute_live_loop_exits jakub at gcc dot gnu.org 2013-01-31 9:05 ` jakub at gcc dot gnu.org 2013-01-31 9:15 ` jakub at gcc dot gnu.org 2013-01-31 11:10 ` jakub at gcc dot gnu.org 2013-01-31 11:45 ` rguenth at gcc dot gnu.org 2013-01-31 11:54 ` rguenth at gcc dot gnu.org [this message] 2013-01-31 11:59 ` rguenth at gcc dot gnu.org 2013-01-31 14:46 ` rguenth at gcc dot gnu.org 2013-01-31 14:54 ` rguenth at gcc dot gnu.org 2013-01-31 16:53 ` rguenth at gcc dot gnu.org 2013-01-31 16:54 ` rguenth 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-56157-4-5OuJzoreBB@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).