This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
I have tracked the --disable-checking bootstrap failure to the assertification of tree-cfg.c. However, the bug is not a misapplied assert, or an assert with sideeffects. It must reside elsewhere.
I attach a patch which reinserts the check with an abort, but this is obviously papering over the problem.
I've attached a preprocessed tree-cfg.i file, with this patch applied (line 24410). Removing that line causes miscompilation of the file on (at least) i686-pc-linux-gnu, with '-O2 -g'.
It's getting to the end of the day here, and I'm going to have another learning curve figuring out where to look next. anyone want to help?
nathan -- Nathan Sidwell :: http://www.codesourcery.com :: CodeSourcery LLC nathan@codesourcery.com :: http://www.planetfall.pwp.blueyonder.co.uk
Index: tree-cfg.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/tree-cfg.c,v
retrieving revision 2.49
diff -c -3 -p -r2.49 tree-cfg.c
*** tree-cfg.c 10 Sep 2004 08:58:46 -0000 2.49
--- tree-cfg.c 10 Sep 2004 15:41:03 -0000
*************** tree_find_edge_insert_loc (edge e, block
*** 2894,2899 ****
--- 2894,2900 ----
if (!is_gimple_val (op))
{
gcc_assert (TREE_CODE (op) == MODIFY_EXPR);
+ if (TREE_CODE (op) != MODIFY_EXPR) abort ();
bsi_insert_before (bsi, op, BSI_NEW_STMT);
TREE_OPERAND (tmp, 0) = TREE_OPERAND (op, 0);
}
Attachment:
tree-cfg.i.gz
Description: application/gunzip
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |