public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/13066] [tree-ssa] ICE in in invert_truthvalue, at fold-const.c:2554
Date: Sun, 29 Feb 2004 01:25:00 -0000 [thread overview]
Message-ID: <20040229012530.18202.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031116043358.13066.bryner@brianryner.com>
------- Additional Comments From pinskia at gcc dot gnu dot org 2004-02-29 01:25 -------
Actually it is fold which is causing this bug.
fold is changing:
<ne_expr 0x4169a5c4
type <boolean_type 0x4169bba0 bool unsigned SI
size <integer_cst 0x41698360 constant invariant 32>
unit size <integer_cst 0x41698400 constant invariant 4>
align 32 symtab 0 alias set -1 precision 1 min <integer_cst 0x416985c0 0> max <
integer_cst 0x41698600 1>>
arg 0 <eq_expr 0x4169a534
type <integer_type 0x4169b8b8 int SI size <integer_cst 0x41698360 32> unit size <
integer_cst 0x41698400 4>
align 32 symtab 0 alias set -1 precision 32 min <integer_cst 0x416983c0 -
2147483648> max <integer_cst 0x416983e0 2147483647>
pointer_to_this <pointer_type 0x416a77c0>>
arg 0 <var_decl 0x4176083c a type <integer_type 0x4169b8b8 int>
asm_written used public static tree_1 SI file pr13066.cc line 3 size <integer_cst
0x41698360 32> unit size <integer_cst 0x41698400 4>
align 32
(mem/f:SI (symbol_ref:SI ("!D__a") [flags 0x2] <var_decl 0x4176083c a>) [0 a+0
S4 A32]) chain <var_decl 0x417607c0 c>>
arg 1 <integer_cst 0x416adc60 constant invariant 0>>
arg 1 <truth_orif_expr 0x4169a558 type <integer_type 0x4169b8b8 int>
arg 0 <ne_expr 0x4169a57c type <integer_type 0x4169b8b8 int>
arg 0 <var_decl 0x417608b8 b>
arg 1 <integer_cst 0x41698ae0 constant invariant 0>>
arg 1 <eq_expr 0x4169a5a0 type <integer_type 0x4169b8b8 int>
arg 0 <var_decl 0x41760744 g> arg 1 <var_decl 0x417607c0 c>>>>
into the expression invoving the TRUTH_XOR_EXPR which is wrong as the type of arg1
is an integer_type at this point.
--
What |Removed |Added
----------------------------------------------------------------------------
AssignedTo|amacleod at redhat dot com |unassigned at gcc dot gnu
| |dot org
Status|ASSIGNED |NEW
Component|optimization |middle-end
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=13066
next prev parent reply other threads:[~2004-02-29 1:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-16 4:34 [Bug optimization/13066] New: " bryner at brianryner dot com
2003-11-16 4:35 ` [Bug optimization/13066] " bryner at brianryner dot com
2003-11-16 5:24 ` bryner at brianryner dot com
2003-11-16 5:28 ` [Bug optimization/13066] [tree-ssa] " bryner at brianryner dot com
2003-11-16 8:41 ` pinskia at gcc dot gnu dot org
2003-11-16 18:51 ` pinskia at gcc dot gnu dot org
2003-11-16 18:53 ` pinskia at gcc dot gnu dot org
2003-12-01 4:29 ` pinskia at gcc dot gnu dot org
2004-01-10 0:52 ` steven at gcc dot gnu dot org
2004-01-20 8:51 ` bryner at brianryner dot com
2004-01-20 9:32 ` bryner at brianryner dot com
2004-01-20 15:55 ` pinskia at gcc dot gnu dot org
2004-02-29 1:25 ` pinskia at gcc dot gnu dot org [this message]
2004-02-29 1:39 ` [Bug middle-end/13066] " pinskia at gcc dot gnu dot org
2004-02-29 2:11 ` pinskia at gcc dot gnu dot org
2004-03-01 19:18 ` cvs-commit at gcc dot gnu dot org
2004-03-01 19:21 ` pinskia 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=20040229012530.18202.qmail@sources.redhat.com \
--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).