On Fri, Apr 27, 2012 at 4:45 PM, Dodji Seketeli wrote:
> Dodji Seketeli writes:
>
>
>> Tested on x86_64-unknown-linux-gnu against trunk. Bootstrap is still
>> running ...
>>
>> * builtins.c (fold_builtin_next_arg): Unwinds to the first
>> location in real source code.
>> ---
>> gcc/
Dodji Seketeli writes:
> Tested on x86_64-unknown-linux-gnu against trunk. Bootstrap is still
> running ...
>
> * builtins.c (fold_builtin_next_arg): Unwinds to the first
> location in real source code.
> ---
> gcc/builtins.c | 23 +++
> 1 files changed, 19 in
Gabriel Dos Reis writes:
> On Wed, Apr 25, 2012 at 10:20 AM, Dodji Seketeli wrote:
>> Gabriel Dos Reis writes:
>>
>>> On Wed, Apr 25, 2012 at 9:04 AM, Dodji Seketeli wrote:
In gcc/testsuite/gcc.dg/pr30457.c, the first warning was not being
emitted because the relevant location was in
On Wed, Apr 25, 2012 at 10:20 AM, Dodji Seketeli wrote:
> Gabriel Dos Reis writes:
>
>> On Wed, Apr 25, 2012 at 9:04 AM, Dodji Seketeli wrote:
>>> In gcc/testsuite/gcc.dg/pr30457.c, the first warning was not being
>>> emitted because the relevant location was inside the var_start macro
>>> defin
Gabriel Dos Reis writes:
> On Wed, Apr 25, 2012 at 9:04 AM, Dodji Seketeli wrote:
>> In gcc/testsuite/gcc.dg/pr30457.c, the first warning was not being
>> emitted because the relevant location was inside the var_start macro
>> defined in a system header. It can even point to a token for a
>> bu
On Wed, Apr 25, 2012 at 9:04 AM, Dodji Seketeli wrote:
> In gcc/testsuite/gcc.dg/pr30457.c, the first warning was not being
> emitted because the relevant location was inside the var_start macro
> defined in a system header. It can even point to a token for a
> builtin macro there. This patch un
