From: Paul Eggert <eggert@cs.ucla.edu>
To: Ralf Wildenhues <Ralf.Wildenhues@gmx.de>
Cc: Andy Wingo <wingo@pobox.com>, bug-guile <bug-guile@gnu.org>,
bug-autoconf@gnu.org
Subject: Re: bug in check for stack growth direction in _AC_LIBOBJ_ALLOCA
Date: Sun, 19 Jun 2011 23:50:24 -0700 [thread overview]
Message-ID: <4DFEEDB0.6030604@cs.ucla.edu> (raw)
In-Reply-To: <20110620063512.10360@gmx.net>
On 06/19/11 23:35, Ralf Wildenhues wrote:
> If you don't use volatile, the compiler is pretty much free to give you
> whatever answer it likes today.
It's true that the test relies on undefined behavior, and so the
compiler is free to do whatever it wants, but I don't see how
adding "volatile" helps, for this particular test. Whatever reasoning
the compiler can do without "volatile", it can also do with "volatile",
for this test.
(I have more confidence in the revised test, because this
time I actually ran it on an x86-64 host with GCC 4.6.0. :-)
next prev parent reply other threads:[~2011-06-20 6:50 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 [this message]
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
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=4DFEEDB0.6030604@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=Ralf.Wildenhues@gmx.de \
--cc=bug-autoconf@gnu.org \
--cc=bug-guile@gnu.org \
--cc=wingo@pobox.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).