zsh-workers
 help / color / mirror / code / Atom feed
From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: 4.0.1-pre-1 on RH6.2
Date: Mon, 19 Feb 2001 11:25:34 +0100 (MET)	[thread overview]
Message-ID: <200102191025.LAA11855@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Bart Schaefer"'s message of Sun, 18 Feb 2001 01:21:48 +0000


Bart Schaefer wrote:

> On Feb 17, 12:51am, Peter Stephenson wrote:
> } Subject: Re: 4.0.1-pre-1 on RH6.2
> }
> } "Bart Schaefer" wrote:
> } > 
> } > zftp.c: In function `zfgetline':
> } > zftp.c:730: warning: variable `added' might be clobbered by `longjmp'
> } 
> } These have always been there and I've never been able to understand what
> } it's talking about with those particular variables.
> 
> Ah, I see.  It's warning you which variables have been given register
> storage allocation by the compiler, and which therefore won't be unwound
> properly when longjmp() takes you back up the stack to the setjmp() spot.
> As long as none of those are referenced in the `if (setjmp(...)) { ... }'
> blocks (which appears to be true), everything should be OK.

Yes, I had a look at that, too , when I first saw it. We can get rid
of the warnings by sticking `volatile' before the declarations if we care.

Bye
 Sven


--
Sven Wischnowsky                         wischnow@informatik.hu-berlin.de


             reply	other threads:[~2001-02-19 10:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-02-19 10:25 Sven Wischnowsky [this message]
2001-02-19 10:37 ` Andrej Borsenkow
  -- strict thread matches above, loose matches on Subject: below --
2001-02-15 17:14 Bart Schaefer
2001-02-15 17:31 ` Fletch
2001-02-15 18:04   ` Bart Schaefer
2001-02-15 19:31     ` Fletch
2001-02-17  0:51 ` Peter Stephenson
2001-02-18  1:21   ` Bart Schaefer

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200102191025.LAA11855@beta.informatik.hu-berlin.de \
    --to=wischnow@informatik.hu-berlin.de \
    --cc=zsh-workers@sunsite.dk \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).