This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [patch win32]: fix for PR target/41943
- From: Richard Henderson <rth at redhat dot com>
- To: Kai Tietz <ktietz70 at googlemail dot com>
- Cc: Danny Smith <dannysmith at clear dot net dot nz>, Dave Korn <dave dot korn dot cygwin at googlemail dot com>, GCC Patches <gcc-patches at gcc dot gnu dot org>
- Date: Wed, 21 Jul 2010 13:41:21 -0700
- Subject: Re: [patch win32]: fix for PR target/41943
- References: <AANLkTilGVoqZEk-zlH-SWCfDNuQEYInJK2GiIiriDihq@mail.gmail.com>
On 07/21/2010 12:38 PM, Kai Tietz wrote:
> +if test x"$user_headers_inc_next_pre" = x
> +then user_headers_inc_next_pre=; fi
> +
> +if test x"$user_headers_inc_next_post" = x
> +then user_headers_inc_next_post=; fi
...
> +# Expand user_headers_inc_next_pre to user_headers_inc_next_pre_list
> +for file in ${user_headers_inc_next_pre} ; do
> + user_headers_inc_next_pre_list="${user_headers_inc_next_pre_list} ${file}"
> +done
> +
> +# Expand user_headers_inc_next_post to user_headers_inc_next_post_list
> +for file in ${user_headers_inc_next_post} ; do
> + user_headers_inc_next_post_list="${user_headers_inc_next_post_list} ${file}"
> +done
I don't understand the point of these. As far as I can tell this
just assigns the contents of foo to foo_list, but in a complicated
and confusing way.
This is unlike the code immediately above that creates extra_headers_list
which in fact prepends a path to each of the entries in the list.
r~