From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: [Patch] Fix configure test for __libc_stack_end
Date: 27 Jul 2003 16:03:11 +0200 [thread overview]
Message-ID: <871xwct6cg.fsf@zagadka.ping.de> (raw)
In-Reply-To: <uw54r2nyca7.fsf@saturn.math.uni-magdeburg.de>
Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de> writes:
> The test for `guile_cv_have_libc_stack_end' does not work reliably
> because the compiler can optimize away the use of the variable in the
> test program. This happened to me on Solaris with the Sun Forte C
> compiler.
>
> Here is a patch.
Thanks! Applied with a minor change: Although the program is never
run, I still feel nervous about printing the stack end as "%s". I
changed that to "%p".
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-07-27 14:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-18 9:18 [Patch] Fix configure test for __libc_stack_end Matthias Koeppe
2003-07-27 14:03 ` Marius Vollmer [this message]
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=871xwct6cg.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@gnu.org \
/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).