public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47002] New: segmentation fault in find_uses_to_rename_use
Date: Sat, 18 Dec 2010 12:45:00 -0000 [thread overview]
Message-ID: <bug-47002-4@http.gcc.gnu.org/bugzilla/> (raw)
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47002
Summary: segmentation fault in find_uses_to_rename_use
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: dcb314@hotmail.com
Created attachment 22809
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=22809
C source code
I just tried to compile package covered-0.7.7 with the latest 4.6
snapshot 20101211 on a Fedora Linux box. The compiler said
../src/vector.c: In function 'vector_set_value_ulong':
../src/vector.c:1857:6: internal compiler error: Segmentation fault
Please submit a full bug report,
with preprocessed source if appropriate.
See <http://gcc.gnu.org/bugs.html> for instructions.
valgrind says
==11010== Invalid read of size 8
==11010== at 0x8B1809: find_uses_to_rename_use (tree-ssa-loop-manip.c:1246)
==11010== by 0x8B1A27: find_uses_to_rename_bb (tree-ssa-loop-manip.c:301)
==11010== by 0x8B216D: rewrite_into_loop_closed_ssa
(tree-ssa-loop-manip.c:331)
==11010== by 0x82A239: distribute_loop (tree-loop-distribution.c:1020)
==11010== by 0x82B15C: tree_loop_distribution
(tree-loop-distribution.c:1146)
==11010== by 0x74510E: execute_one_pass (passes.c:1553)
==11010== by 0x7453B4: execute_pass_list (passes.c:1608)
==11010== by 0x7453C6: execute_pass_list (passes.c:1609)
==11010== by 0x7453C6: execute_pass_list (passes.c:1609)
==11010== by 0x838CD5: tree_rest_of_compilation (tree-optimize.c:422)
==11010== by 0x9D6540: cgraph_expand_function (cgraphunit.c:1508)
==11010== by 0x9D8AA9: cgraph_optimize (cgraphunit.c:1567)
==11010== Address 0x10 is not stack'd, malloc'd or (recently) free'd
==11010==
Source code attached. Flag -O3 required.
next reply other threads:[~2010-12-18 12:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-18 12:45 dcb314 at hotmail dot com [this message]
2010-12-18 14:26 ` [Bug c/47002] [4.6 Regression] " hjl.tools at gmail dot com
2010-12-20 5:23 ` [Bug tree-optimization/47002] " spop at gcc dot gnu.org
2010-12-20 5:25 ` spop at gcc dot gnu.org
2010-12-22 6:24 ` spop at gcc dot gnu.org
2010-12-23 16:26 ` spop at gcc dot gnu.org
2010-12-31 11:19 ` jakub at gcc dot gnu.org
2010-12-31 12:43 ` dcb314 at hotmail dot com
2010-12-31 14:13 ` 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=bug-47002-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).