[Bug tree-optimization/24599] [4.0 regression] segv after overflow detection

2005-11-04 Thread rakdver at gcc dot gnu dot org
--- Comment #4 from rakdver at gcc dot gnu dot org 2005-11-04 13:39 --- Nevertheless, the fact that boolean_true_node has overflow flag set is wrong, this should not happen -- shared constants should not be modified. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24599

[Bug tree-optimization/24599] [4.0 regression] segv after overflow detection

2005-11-04 Thread rakdver at gcc dot gnu dot org
--- Comment #5 from rakdver at gcc dot gnu dot org 2005-11-04 14:02 --- This happens in c-typeck.c:build_c_cast: value = convert (type, value); /* Ignore any integer overflow caused by the cast. */ if (TREE_CODE (value) == INTEGER_CST) { /* If

[Bug tree-optimization/24599] [4.0 regression] segv after overflow detection

2005-11-03 Thread dje at transmeta dot com
--- Comment #2 from dje at transmeta dot com 2005-11-03 18:18 --- I'm not sure the root cause of this bug is fixed in 4.1. It looks to me like it's still there and is only (currently) hidden. Am I mistaken? Apply this patch to gcc-4.1-20051029 and recompile the testcase with -O3. I'm

[Bug tree-optimization/24599] [4.0 regression] segv after overflow detection

2005-11-03 Thread pinskia at gcc dot gnu dot org
--- Comment #3 from pinskia at gcc dot gnu dot org 2005-11-03 18:25 --- (In reply to comment #2) I'm not sure the root cause of this bug is fixed in 4.1. It looks to me like it's still there and is only (currently) hidden. Am I mistaken? Apply this patch to gcc-4.1-20051029 and

[Bug tree-optimization/24599] [4.0 regression] segv after overflow detection

2005-11-01 Thread pinskia at gcc dot gnu dot org
-- pinskia at gcc dot gnu dot org changed: What|Removed |Added Target Milestone|--- |4.0.3 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24599

[Bug tree-optimization/24599] [4.0 regression] segv after overflow detection

2005-10-31 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-10-31 20:09 --- Confirmed, only a 4.0 regression. Back trace: #0 0x004a1ff2 in find_interesting_uses_cond (data=0x7fc1d340, stmt=0x2afc0320, cond_p=0x2afc0358) at