public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "doko at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/56398] New: [4.8 Regression] ICE (Segmentation fault) in dominated_by_p
Date: Tue, 19 Feb 2013 15:03:00 -0000 [thread overview]
Message-ID: <bug-56398-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56398
Bug #: 56398
Summary: [4.8 Regression] ICE (Segmentation fault) in
dominated_by_p
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: doko@gcc.gnu.org
Created attachment 29498
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=29498
preprocessed source
works with the 4.7 branch, fails with trunk 20130217. lowering optimization to
-O2 avoids the issue.
$ g++ -c -g -O3 vtkLargeInteger.ii
/home/packages/tmp/ice/vtk-5.8.0/Common/vtkLargeInteger.cxx: In function 'long
int vtkpow(long int, long int)':
/home/packages/tmp/ice/vtk-5.8.0/Common/vtkLargeInteger.cxx:36:6: internal
compiler error: Segmentation fault
long vtkpow(long a, long b)
^
Please submit a full bug report,
with preprocessed source if appropriate.
Program received signal SIGSEGV, Segmentation fault.
0x00000000006ea65b in dominated_by_p(cdi_direction, basic_block_def const*,
basic_block_def const*) ()
(gdb) bt
#0 0x00000000006ea65b in dominated_by_p(cdi_direction, basic_block_def const*,
basic_block_def const*) ()
#1 0x0000000000a2e450 in ?? ()
#2 0x0000000000a30101 in ?? ()
#3 0x0000000000a31b26 in vect_do_peeling_for_loop_bound(_loop_vec_info*,
tree_node**, unsigned int, bool) ()
#4 0x0000000000a22404 in vect_transform_loop(_loop_vec_info*) ()
#5 0x0000000000a3ac3b in vectorize_loops() ()
#6 0x0000000000860919 in execute_one_pass(opt_pass*) ()
#7 0x0000000000860cf5 in execute_pass_list(opt_pass*) ()
#8 0x0000000000860d07 in execute_pass_list(opt_pass*) ()
#9 0x0000000000860d07 in execute_pass_list(opt_pass*) ()
#10 0x00000000006c03be in ?? ()
#11 0x00000000006c1977 in compile() ()
#12 0x00000000006c1d9a in finalize_compilation_unit() ()
#13 0x0000000000595fe9 in cp_write_global_declarations() ()
#14 0x00000000008eee8d in ?? ()
#15 0x00000000008f08fa in toplev_main(int, char**) ()
#16 0x00007ffff6c55a55 in __libc_start_main (main=0x533f50 <main>, argc=15,
ubp_av=0x7fffffffe508, init=<optimized out>, fini=<optimized out>,
rtld_fini=<optimized out>, stack_end=0x7fffffffe4f8) at libc-start.c:260
#17 0x00000000005341b9 in _start ()
next reply other threads:[~2013-02-19 15:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 15:03 doko at gcc dot gnu.org [this message]
2013-02-20 9:32 ` [Bug tree-optimization/56398] " rguenth at gcc dot gnu.org
2013-02-20 9:51 ` mpolacek at gcc dot gnu.org
2013-02-20 10:07 ` rguenth at gcc dot gnu.org
2013-02-20 10:09 ` rguenth at gcc dot gnu.org
2013-02-20 13:38 ` rguenth at gcc dot gnu.org
2013-02-20 13:49 ` rguenth at gcc dot gnu.org
2013-02-20 15:34 ` mpolacek at gcc dot gnu.org
2013-02-21 8:58 ` rguenther at suse dot de
2013-02-21 10:29 ` mpolacek 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-56398-4@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).