From: "Ralf Wildenhues" <Ralf.Wildenhues@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: bug-guile <bug-guile@gnu.org>,
bug-autoconf@gnu.org, bug-gnulib <bug-gnulib@gnu.org>,
Eric Blake <eblake@redhat.com>
Subject: Re: bug in check for stack growth direction in _AC_LIBOBJ_ALLOCA
Date: Tue, 21 Jun 2011 21:43:49 +0200 [thread overview]
Message-ID: <20110621194349.188990@gmx.net> (raw)
In-Reply-To: <4DFFC76D.7000703@cs.ucla.edu>
* Paul Eggert wrote on Tue, Jun 21, 2011 at 12:19:25AM CEST:
> Testing this is not something for the fainthearted, as it requires
> access to all sorts of strange hosts. However, it does seem to
> defeat GCC 4.6.0's tail-recursion optimization (-O0 through -O4)
> on my platform, which is what is wanted.
It would be good to make sure GCC 4.6 whole program/link time
optimization doesn't defeat this (I haven't checked).
Thanks,
Ralf
next prev parent reply other threads:[~2011-06-21 19:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-17 10:21 bug in check for stack growth direction in _AC_LIBOBJ_ALLOCA Andy Wingo
2011-06-18 20:25 ` Andrew W. Nosenko
2011-06-19 19:03 ` Andy Wingo
2011-06-20 8:25 ` Andrew W. Nosenko
2011-06-20 10:24 ` Andrew W. Nosenko
2011-06-18 21:42 ` Paul Eggert
2011-06-19 19:01 ` Andy Wingo
2011-06-20 5:35 ` Paul Eggert
2011-06-20 6:35 ` Ralf Wildenhues
2011-06-20 6:50 ` Paul Eggert
2011-06-20 8:18 ` Andrew W. Nosenko
2011-06-20 8:01 ` Andy Wingo
2011-06-20 17:54 ` Eric Blake
2011-06-20 22:19 ` Paul Eggert
2011-06-21 19:43 ` Ralf Wildenhues [this message]
2011-06-21 20:08 ` Paul Eggert
2011-06-20 17:56 ` Eric Blake
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=20110621194349.188990@gmx.net \
--to=ralf.wildenhues@gmx.de \
--cc=bug-autoconf@gnu.org \
--cc=bug-gnulib@gnu.org \
--cc=bug-guile@gnu.org \
--cc=eblake@redhat.com \
--cc=eggert@cs.ucla.edu \
/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).