From: Kyle McMartin <kyle@mcmartin.ca>
To: Neil Jerram <neiljerram@googlemail.com>
Cc: debian-hppa@lists.debian.org, guile-devel@gnu.org
Subject: Re: Guile FTBFS on hppa - problem in detecting stack direction?
Date: Wed, 6 Aug 2008 17:13:00 -0400 [thread overview]
Message-ID: <20080806211259.GB3281@phobos.i.cabal.ca> (raw)
In-Reply-To: <49dd78620808061338k3c29bd77o9d38d0706e0c5dca@mail.gmail.com>
On Wed, Aug 06, 2008 at 09:38:32PM +0100, Neil Jerram wrote:
> Hi hppa people! I'm hoping you can help me fix a FTBFS that we're
> getting with Guile on hppa.
>
> The build log is here:
> http://buildd.debian.org/fetch.cgi?pkg=guile-1.8;ver=1.8.5%2B1-2;arch=hppa;stamp=1217809852
>
> The specific problem is a segmentation fault, at a point in a build
> that probably won't mean anything to non-Guile folks - but the key
> point is that we were recently seeing exactly the same segmentation
> fault (i.e. at the same place) on several other architectures (mips,
> mipsel, powerpc), and that was caused by the code in configure.in not
> detecting the stack direction properly.
>
> This patch - http://git.savannah.gnu.org/gitweb/?p=guile.git;a=commit;h=9143131b2766d1e29e05d61b5021395b4c93a6bc
> - fixed the problem for mips, mipsel and powerpc, but it looks as
> though we are still getting the stack direction wrong on hppa. (My
> understanding is that on hppa the stack actually grows upwards,
> whereas on most platforms it's downwards.)
>
> I've appended the relevant bit of configure.in below. Can anyone help
> with why this might not be working on hppa?
>
According to the build.log,
checking stack direction... (cached) 0
this looks like it's obtaining the wrong result...
I'm not entirely sure why... what optimization pass is being used to
build this?
regards, Kyle
> Thanks,
> Neil
>
> #--------------------------------------------------------------------
> #
> # 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_CACHE_CHECK([stack direction],
> [SCM_I_GSC_STACK_GROWS_UP],
> [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)])])
>
>
> --
> To UNSUBSCRIBE, email to debian-hppa-REQUEST@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
>
next prev parent reply other threads:[~2008-08-06 21:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 20:38 Guile FTBFS on hppa - problem in detecting stack direction? Neil Jerram
2008-08-06 21:13 ` Kyle McMartin [this message]
2008-08-07 1:40 ` Carlos O'Donell
2008-08-07 9:49 ` Bernhard R. Link
2008-08-07 12:29 ` Carlos O'Donell
2008-08-09 13:31 ` Greg Troxel
2008-08-09 15:16 ` Han-Wen Nienhuys
2008-08-07 12:27 ` Carlos O'Donell
2008-08-07 21:04 ` Neil Jerram
2008-08-09 17:02 ` Kyle McMartin
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
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080806211259.GB3281@phobos.i.cabal.ca \
--to=kyle@mcmartin.ca \
--cc=debian-hppa@lists.debian.org \
--cc=guile-devel@gnu.org \
--cc=neiljerram@googlemail.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).