[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: bug in check for stack growth direction in _AC_LIBOBJ_ALLOCA

From: Andy Wingo
Subject: Re: bug in check for stack growth direction in _AC_LIBOBJ_ALLOCA
Date: Sun, 19 Jun 2011 21:03:45 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.3 (gnu/linux)


On Sat 18 Jun 2011 22:25, "Andrew W. Nosenko" <address@hidden> writes:

> On Fri, Jun 17, 2011 at 13:21, Andy Wingo <address@hidden> wrote:
>> address@hidden:/tmp$ cat foo.c
>>  int
>>  find_stack_direction ()
>>  {
>>    static char *addr = 0;
> Try to rewrite this line as
>         volatile static char *addr = 0;
> It should help.

It didn't, unfortunately.

This issue can be reproduced on a stock Debian unstable system with
gcc-4.6, btw.

>> I don't know what allows GCC to do this inlining.  Could it be a GCC
>> bug?  Every time I think I have a GCC bug I'm wrong, though :)
> No.  It indeed traceable.  Just start from main() and you will have
> full trace even with pen and paper.

Apologies for the ignorant question, but what does "trace" mean? :)



reply via email to

[Prev in Thread] Current Thread [Next in Thread]