From: gs-cygwin.com@gluelogic.com
To: cygwin@cygwin.com
Subject: Re: stack grow direction wrongly detected
Date: Fri, 5 Mar 2021 09:43:26 -0500 [thread overview]
Message-ID: <YEJDjnDYbV7RXsqw@xps13> (raw)
In-Reply-To: <20210305233104.782838da83161a90f56a5369@nifty.ne.jp>
On Fri, Mar 05, 2021 at 11:31:04PM +0900, Takashi Yano via Cygwin wrote:
> On Fri, 5 Mar 2021 13:18:38 +0100
> Marco Atzeri wrote:
> > Hi Guys,
> > noted trying to rebuild guile 1.8.8.
> >
> > The following piece of code in the past
> > was setting SCM_I_GSC_STACK_GROWS_UP=0
> > and now produces SCM_I_GSC_STACK_GROWS_UP=1
> >
> > I assume some change in the gcc compiler is causing the issue.
> > I presume most of the programs and libraries do not care,
> > but some special one like guile crashes during build for this issue,
> > so be aware.
> >
> > Regards
> > Marco
> >
> >
> > #--------------------------------------------------------------------
> > #
> > # Which way does the stack grow?
> > #
> > # Following code comes from Autoconf 2.61's internal _AC_LIBOBJ_ALLOCA
> > # macro (/usr/share/autoconf/autoconf/functions.m4). Gnulib has
> > # very similar code, so in future we could look at using that.
> > #
> > # An important detail is that the code involves find_stack_direction
> > # calling _itself_ - which means that find_stack_direction (or at
> > # least the second find_stack_direction() call) cannot be inlined.
> > # If the code could be inlined, that might cause the test to give
> > # an incorrect answer.
> > #--------------------------------------------------------------------
> >
> > SCM_I_GSC_STACK_GROWS_UP=0
> > AC_RUN_IFELSE([AC_LANG_SOURCE(
> > [AC_INCLUDES_DEFAULT
> > int
> > find_stack_direction ()
> > {
> > static char *addr = 0;
> > auto char dummy;
> > if (addr == 0)
> > {
> > addr = &dummy;
> > return find_stack_direction ();
> > }
> > else
> > return (&dummy > addr) ? 1 : -1;
> > }
> >
> > int
> > main ()
> > {
> > return find_stack_direction () < 0;
> > }])],
> > [SCM_I_GSC_STACK_GROWS_UP=1],
> > [],
> > [AC_MSG_WARN(Guessing that stack grows down -- see
> > scmconfig.h)])
>
> This seems to be a result of optimization. With gcc v10.2.0,
> the return value of the code is:
> -O0: 1
> -O1: 1
> -O2: 0
> -O3: 1
> -O4: 1
>
> If find_stack_direction() is implemented as recursive call,
> and auto variable is allocated in the stack every time,
> in the first call, addr is initialized to the first stack
> position, and in the second call, second address of dummy
> is reduced because stack of x86 is reverse direction.
> Therefore (&dummy > addr) ? 1 : -1; returns -1.
> As a result, the return value find_stack_direction() < 0
> is 1. With -O0 or -O1 this implemented as recursive call,
> so the return value is 1.
If the compiler is gcc or clang:
__attribute__(__noinline__)
int
find_stack_direction ()
{
...
}
Cheers, Glenn
next prev parent reply other threads:[~2021-03-05 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-05 12:18 Marco Atzeri
2021-03-05 14:31 ` Takashi Yano
2021-03-05 14:43 ` gs-cygwin.com [this message]
2021-03-06 8:29 ` Marco Atzeri
2021-03-06 9:29 ` Thomas Wolff
2021-03-05 15:25 ` Thomas Wolff
2021-03-05 18:58 ` Brian Inglis
2021-03-05 20:29 ` Marco Atzeri
2021-03-06 1:06 ` Takashi Yano
2021-03-06 9:12 ` Marco Atzeri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YEJDjnDYbV7RXsqw@xps13 \
--to=gs-cygwin.com@gluelogic.com \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).