public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/51994] [4.6/4.7 Regression] git-1.7.8.3 miscompiled due to negative bitpos from get_inner_reference
Date: Wed, 25 Jan 2012 14:10:00 -0000	[thread overview]
Message-ID: <bug-51994-4-Voe1qvDnYG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-51994-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #8 from Uros Bizjak <ubizjak at gmail dot com> 2012-01-25 13:33:43 UTC ---
And the test in Comment #7 exposed the same problem in extract_bit_field & co.

#19 0x00000000005801f4 in extract_bit_field (str_rtx=0x2aaaae85b760,
bitsize=46912560805760, bitnum=46912559843392, 
    unsignedp=370, packedp=<value optimized out>, target=0x0, mode=QImode,
tmode=QImode)
---Type <return> to continue, or q <return> to quit---
    at ../../gcc-svn/branches/gcc-4_6-branch/gcc/expmed.c:1697
#20 0x000000000058aa12 in expand_expr_real_1 (exp=0x2aaaae773870,
target=0x2aaaae85b700, tmode=<value optimized out>, 
    modifier=<value optimized out>, alt_rtl=<value optimized out>)
    at ../../gcc-svn/branches/gcc-4_6-branch/gcc/expr.c:9380

What a can of worms...


  parent reply	other threads:[~2012-01-25 13:34 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-25 10:30 [Bug tree-optimization/51994] New: " ubizjak at gmail dot com
2012-01-25 10:30 ` [Bug tree-optimization/51994] " ubizjak at gmail dot com
2012-01-25 11:10 ` [Bug middle-end/51994] " rguenth at gcc dot gnu.org
2012-01-25 11:22 ` ebotcazou at gcc dot gnu.org
2012-01-25 11:57 ` ubizjak at gmail dot com
2012-01-25 12:02 ` ubizjak at gmail dot com
2012-01-25 13:00 ` rguenth at gcc dot gnu.org
2012-01-25 13:06 ` rguenth at gcc dot gnu.org
2012-01-25 13:30 ` ubizjak at gmail dot com
2012-01-25 14:10 ` ubizjak at gmail dot com [this message]
2012-01-25 14:44 ` ubizjak at gmail dot com
2012-01-25 15:00 ` ubizjak at gmail dot com
2012-01-25 15:14 ` jakub at gcc dot gnu.org
2012-01-25 19:07 ` ubizjak at gmail dot com
2012-01-25 19:21 ` ubizjak at gmail dot com
2012-01-25 20:25 ` ubizjak at gmail dot com
2012-01-25 20:29 ` jakub at gcc dot gnu.org
2012-01-26  9:31 ` ubizjak at gmail dot com
2012-01-26  9:32 ` jakub at gcc dot gnu.org
2012-01-26  9:36 ` ubizjak at gmail dot com
2012-01-26 10:29 ` rguenth at gcc dot gnu.org
2012-01-26 12:36 ` ebotcazou at gcc dot gnu.org
2012-01-26 19:43 ` ubizjak at gmail dot com
2012-01-26 20:40 ` ubizjak at gmail dot com
2012-01-26 21:02 ` ubizjak at gmail dot com
2012-01-26 22:28 ` ebotcazou at gcc dot gnu.org
2012-02-01 15:34 ` ebotcazou at gcc dot gnu.org
2012-02-01 15:36 ` ebotcazou at gcc dot gnu.org
2012-02-01 15:46 ` rguenth at gcc dot gnu.org
2012-02-01 15:47 ` rguenth at gcc dot gnu.org
2012-02-01 15:51 ` ebotcazou at gcc dot gnu.org
2012-02-01 15:54 ` ebotcazou at gcc dot gnu.org
2012-02-01 16:02 ` rguenther at suse dot de
2012-02-01 16:36 ` ebotcazou at gcc dot gnu.org
2012-02-01 18:42 ` ubizjak at gmail dot com
2012-02-02  8:57 ` rguenther at suse dot de
2012-02-06 12:29 ` ebotcazou at gcc dot gnu.org
2012-02-07 15:43 ` rguenth at gcc dot gnu.org
2012-02-07 17:22 ` ebotcazou at gcc dot gnu.org
2012-02-07 17:25 ` ebotcazou at gcc dot gnu.org
2012-02-07 17:28 ` ebotcazou 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-51994-4-Voe1qvDnYG@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: 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).