public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "schwab at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/25905]  New: [4.2 regression] ICE in expand_compound_operation
Date: Sat, 21 Jan 2006 23:24:00 -0000	[thread overview]
Message-ID: <bug-25905-50@http.gcc.gnu.org/bugzilla/> (raw)

$ ./xgcc -B./ unwind-dw2-fde-glibc.i -S -O -v
Reading specs from ./specs
Target: m68k-linux
Configured with: ../gcc/configure --prefix=/usr/local/m68k-linux
--host=powerpc-linux --target=m68k-linux
--with-sysroot=/usr/local/m68k-linux/m68k-linux/sys-root --enable-shared
--enable-__cxa_atexit --with-system-zlib
--enable-languages=c,c++,fortran,java,objc --no-create --no-recursion
Thread model: posix
gcc version 4.2.0 20060121 (experimental)
 ./cc1 -fpreprocessed unwind-dw2-fde-glibc.i -quiet -dumpbase
unwind-dw2-fde-glibc.i -auxbase unwind-dw2-fde-glibc -O -version -o
unwind-dw2-fde-glibc.s
GNU C version 4.2.0 20060121 (experimental) (m68k-linux)
        compiled by GNU C version 4.0.2 20050901 (prerelease) (SUSE Linux).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
Compiler executable checksum: 0ad6bd3654ebd3f56f26d23ad96d1796
../../gcc/gcc/unwind-dw2-fde.c: In function
&#8216;fde_single_encoding_compare&#8217;:
../../gcc/gcc/unwind-dw2-fde.c:350: internal compiler error: in
expand_compound_operation, at combine.c:5644

Caused by:

r109961 | bonzini | 2006-01-19 15:54:57 +0100 (Do, 19 Jan 2006) | 13 lines

2006-01-19  Paolo Bonzini  <bonzini@gnu.org>

        * combine.c (try_combine): Do not worry about MEMs wrapped by USEs.
        (expand_compound_operation, expand_field_assignment): Fail if the
        bit lengths of an extract operation are out of range.
        (make_extraction): Compute wanted_inner_mode based on the position
        and length of the extraction.  Make it extraction_mode for non-constant
        positions, and do not modify offset in that case.  When generating a
        new MEM, use a mode that can hold the extraction while keeping correct
        alignment.  Remove code that supported MEMs wrapped by USEs.
        (simplify_shift_const_1, force_to_mode) <case USE>: Remove.


-- 
           Summary: [4.2 regression] ICE in expand_compound_operation
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: ice-on-valid-code
          Severity: normal
          Priority: P3
         Component: middle-end
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: schwab at suse dot de
GCC target triplet: m68k-linux


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


             reply	other threads:[~2006-01-21 23:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-21 23:24 schwab at suse dot de [this message]
2006-01-21 23:25 ` [Bug middle-end/25905] " schwab at suse dot de
2006-01-21 23:41 ` pinskia at gcc dot gnu dot org
2006-01-21 23:44 ` pinskia at gcc dot gnu dot org
2006-01-22 13:41 ` pbrook at gcc dot gnu dot org
2006-01-23  8:14 ` bonzini at gnu dot org
2006-01-23  8:22 ` bonzini at gnu dot org
2006-01-23  8:28 ` bonzini at gnu dot org
2006-01-23  8:47 ` kkojima at gcc dot gnu dot org
2006-01-23 10:01 ` bonzini at gnu dot org
2006-01-23 20:42 ` joel at gcc dot gnu dot org
2006-01-24 14:29 ` bonzini at gcc dot gnu dot org
2006-01-24 14:30 ` bonzini at 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=bug-25905-50@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).