public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "zsojka at seznam dot cz" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug rtl-optimization/44012] ICE: SIGSEGV in ira_merge_allocno_live_ranges
Date: Thu, 06 May 2010 13:51:00 -0000	[thread overview]
Message-ID: <20100506135046.27825.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44012-14164@http.gcc.gnu.org/bugzilla/>



------- Comment #1 from zsojka at seznam dot cz  2010-05-06 13:50 -------
Created an attachment (id=20585)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=20585&action=view)
partially reduced testcase

Compiler flags:
g++ -O1 -fgcse -findirect-inlining -fipa-sra
or
g++ -O2 -fno-strict-aliasing

Valgind output:
$ valgrind --trace-children=yes -q
/mnt/svn/gcc-trunk/binary-159045-lto-fortran/bin/g++ -O1 -fgcse
-findirect-inlining -fipa-sra testcase-min2.ii
==18710== Invalid read of size 4
==18710==    at 0x801A40: ira_merge_allocno_live_ranges (ira-build.c:863)
==18710==    by 0x802C7E: remove_unnecessary_regions (ira-build.c:1977)
==18710==    by 0x804408: ira_build (ira-build.c:2778)
==18710==    by 0x7FEA6E: rest_of_handle_ira (ira.c:3215)
==18710==    by 0x8588AD: execute_one_pass (passes.c:1590)
==18710==    by 0x858B34: execute_pass_list (passes.c:1645)
==18710==    by 0x858B46: execute_pass_list (passes.c:1646)
==18710==    by 0x94CDB5: tree_rest_of_compilation (tree-optimize.c:413)
==18710==    by 0xAD49F5: cgraph_expand_function (cgraphunit.c:1627)
==18710==    by 0xAD7289: cgraph_optimize (cgraphunit.c:1706)
==18710==    by 0xAD7A04: cgraph_finalize_compilation_unit (cgraphunit.c:1166)
==18710==    by 0x550FCA: cp_write_global_declarations (decl2.c:3837)
==18710==  Address 0xafafafafafafafb7 is not stack'd, malloc'd or (recently)
free'd
==18710==
testcase-min2.ii: In member function 'void SQCompiler::BitwiseXorExp()':
testcase-min2.ii:371:2: internal compiler error: Segmentation fault

I will post more reduced testcase, delta is quite slow with this code.


-- 


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


  reply	other threads:[~2010-05-06 13:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-06 12:48 [Bug rtl-optimization/44012] New: " zsojka at seznam dot cz
2010-05-06 13:51 ` zsojka at seznam dot cz [this message]
2010-05-06 14:38 ` [Bug rtl-optimization/44012] " zsojka at seznam dot cz
2010-05-06 14:45 ` hjl dot tools at gmail dot com
2010-05-06 15:05 ` zsojka at seznam dot cz
2010-05-06 15:54 ` zsojka at seznam dot cz
2010-05-06 16:39 ` jamborm at gcc dot gnu dot org
2010-05-06 16:48 ` [Bug rtl-optimization/44012] [4.5/4.6 Regression] " zsojka at seznam dot cz
2010-05-06 18:57 ` hjl dot tools at gmail dot com
2010-05-06 21:01 ` hjl dot tools at gmail dot com
2010-05-07  0:32 ` zsojka at seznam dot cz
2010-05-07  9:46 ` rguenth at gcc dot gnu dot org
2010-05-07 17:49 ` vmakarov at redhat dot com
2010-05-10 14:03 ` hjl at gcc dot gnu dot org
2010-05-10 14:05 ` hjl at gcc dot gnu dot org
2010-05-19 12:54 ` rguenth 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=20100506135046.27825.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: 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).