public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rmansfield at qnx dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/46212] Segfault in reg_nonzero_bits_for_combine
Date: Thu, 28 Oct 2010 18:45:00 -0000	[thread overview]
Message-ID: <20101028184500.8RAE8ePXBjqOX7cZl5Xxwmsr5QHIFa1D6DXHGxHCBlM@z> (raw)
In-Reply-To: <bug-46212-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46212

--- Comment #3 from Ryan Mansfield <rmansfield at qnx dot com> 2010-10-28 18:45:10 UTC ---
Reduced testcase:

static __inline__ unsigned foo(void *__ptr) {
   unsigned __val = *(volatile unsigned *)(__ptr);
   return (((__val) >> 24) | (((__val) >> 8) & 0xff00) |  (((__val) & 0xff00)
<< 8) | ((__val) << 24));
}

void bar(void *dst, void *src, int pixels) {
  unsigned c;
  while (pixels--) {
   c = foo(src);
   *(unsigned *)dst = (c & 0xf80000) >> 9 | (c & 0xf800) >> 6 | (c & 0xf8) >> 3
| (c & 0x80000000) >> 16;
  }
}

Looks like the same bug. Sorry for the dup. I only searched bugzilla for PRs
about reg_nonzero_bits_for_combine.


  parent reply	other threads:[~2010-10-28 18:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-28 17:33 [Bug middle-end/46212] New: " rmansfield at qnx dot com
2010-10-28 17:37 ` [Bug middle-end/46212] " rmansfield at qnx dot com
2010-10-28 17:40 ` pinskia at gcc dot gnu.org
2010-10-28 18:45 ` rmansfield at qnx dot com [this message]
2010-10-29 12:46 ` [Bug rtl-optimization/46212] " ebotcazou at gcc dot gnu.org
2010-10-31 15:50 ` [Bug rtl-optimization/46212] [4.6 regression] segfault " hjl.tools at gmail dot com
2010-11-01 11:24 ` jakub at gcc dot gnu.org
2010-11-01 21:22 ` ebotcazou at gcc dot gnu.org
2010-11-03  8:31 ` jakub at gcc dot gnu.org
2010-11-03  8:45 ` jakub 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=20101028184500.8RAE8ePXBjqOX7cZl5Xxwmsr5QHIFa1D6DXHGxHCBlM@z \
    --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: 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).