From: Andy Wingo <wingo@pobox.com>
To: stefan-husmann@t-online.de
Cc: 25700-done@debbugs.gnu.org
Subject: bug#25700: Undeclared variable stack_top in libguile/continuations.c
Date: Wed, 01 Mar 2017 17:38:34 +0100 [thread overview]
Message-ID: <87inntdkad.fsf@pobox.com> (raw)
In-Reply-To: <87shniwr5a.fsf@frege> (stefan-husmann@t-online.de's message of "Mon, 13 Feb 2017 07:17:53 +0100")
On Mon 13 Feb 2017 07:17, stefan-husmann@t-online.de writes:
> with the latest commit 8e1af70c2c4ccc7fb19afa48ffd4662f95bb0f66 from git I get
>
> CC libguile_2.2_la-continuations.lo
> continuations.c: In function 'scm_i_continuation_to_frame':
> continuations.c:186:7: error: 'stack_top' undeclared (first use in this function)
> stack_top = data->stack_bottom + data->stack_size;
>
> So stack_top is still used, where latest commit's commit message says it is not.
Yeah sorry about that. Fixed :)
Andy
prev parent reply other threads:[~2017-03-01 16:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 6:17 bug#25700: Undeclared variable stack_top in libguile/continuations.c stefan-husmann
2017-03-01 16:38 ` Andy Wingo [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=87inntdkad.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=25700-done@debbugs.gnu.org \
--cc=stefan-husmann@t-online.de \
/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).