OpenE2K/gcc
2
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

gimplify.c (gimplify_init_ctor_eval): Don't discard a zero-sized value if it has side-effects.

Browse Source 
* gimplify.c (gimplify_init_ctor_eval): Don't discard a zero-sized
	value if it has side-effects.

From-SVN: r104262
This commit is contained in:
Olivier Hainque 2005-09-14 06:59:10 +00:00 committed by Olivier Hainque
parent 0df3cf7f04
commit 816fa80a8f
2 changed files with 11 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
gcc/ChangeLog
View File

@ -1,3 +1,8 @@
2005-09-14 Olivier Hainque <hainque@adacore.com>
* gimplify.c (gimplify_init_ctor_eval): Don't discard a zero-sized
value if it has side-effects.
2005-09-14 David Edelsohn <edelsohn@gnu.org>
PR target/22068

7
gcc/gimplify.c
View File

@ -2576,7 +2576,12 @@ gimplify_init_ctor_eval (tree object, VEC(constructor_elt,gc) *elts,
so we don't have to figure out what's missing ourselves. */
gcc_assert (purpose);
if (zero_sized_field_decl (purpose))
/* Skip zero-sized fields, unless value has side-effects. This can
happen with calls to functions returning a zero-sized type, which
we shouldn't discard. As a number of downstream passes don't
expect sets of zero-sized fields, we rely on the gimplification of
the MODIFY_EXPR we make below to drop the assignment statement. */
if (! TREE_SIDE_EFFECTS (value) && zero_sized_field_decl (purpose))
continue;
/* If we have a RANGE_EXPR, we have to build a loop to assign the