public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/35043] New: ICE in tree-data-ref because signed_type_for_types returns NULL
Date: Thu, 31 Jan 2008 17:24:00 -0000 [thread overview]
Message-ID: <bug-35043-10053@http.gcc.gnu.org/bugzilla/> (raw)
1510 type = signed_type_for_types (TREE_TYPE (chrec_a), TREE_TYPE
(chrec_b));
1511 chrec_a = chrec_convert (type, chrec_a, NULL_TREE);
(gdb) p type
$4 = (tree) 0x0
and we then ICE in
#0 0x000000000064bc08 in fold_convert (type=0x0, arg=0x2aad7d1bb570)
at /space/rguenther/src/svn/trunk/gcc/fold-const.c:2496
(gdb) call debug_tree (chrec_a)
<integer_cst 0x2aad7d1bb570 type <integer_type 0x2aad7d1ae0c0 bit_size_type>
constant invariant 1>
(gdb) call debug_tree (chrec_b)
<integer_cst 0x2aad7d1bb390 type <integer_type 0x2aad7d1ae0c0 bit_size_type>
constant invariant 0>
--
Summary: ICE in tree-data-ref because signed_type_for_types
returns NULL
Product: gcc
Version: 4.3.0
Status: UNCONFIRMED
Keywords: ice-on-valid-code
Severity: normal
Priority: P3
Component: tree-optimization
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: rguenth at gcc dot gnu dot org
GCC target triplet: ia64-*-*
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35043
next reply other threads:[~2008-01-31 17:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-31 17:24 rguenth at gcc dot gnu dot org [this message]
2008-01-31 17:31 ` [Bug tree-optimization/35043] " rguenth at gcc dot gnu dot org
2008-01-31 18:40 ` [Bug middle-end/35043] " rguenth at gcc dot gnu dot org
2008-01-31 18:45 ` rguenth at gcc dot gnu dot org
2008-02-04 13:31 ` rguenth at gcc dot gnu dot org
2008-02-04 13:31 ` 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=bug-35043-10053@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).