On Wed, Dec 10, 2014 at 11:07:37AM +0100, Thomas Schwinge wrote:
> ..., I noticed that GIMPLE_OMP_TARGET doesn't walk the child_fn and
> data_arg. Is that intentional, or should that be done? If the latter
> (but this doesn't seem to cause any ill effects -- why?), OK to commit
> the following to trunk?
Ok with proper ChangeLog.
> gcc/gimple-walk.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git gcc/gimple-walk.c gcc/gimple-walk.c
> index bfa3532..1330c04 100644
> --- gcc/gimple-walk.c
> +++ gcc/gimple-walk.c
> @@ -416,6 +416,14 @@ walk_gimple_op (gimple stmt, walk_tree_fn callback_op,
> pset);
> if (ret)
> return ret;
> + ret = walk_tree (gimple_omp_target_child_fn_ptr (stmt), callback_op,
> wi,
> + pset);
> + if (ret)
> + return ret;
> + ret = walk_tree (gimple_omp_target_data_arg_ptr (stmt), callback_op,
> wi,
> + pset);
> + if (ret)
> + return ret;
> break;
>
> case GIMPLE_OMP_TEAMS:
Jakub
