Git development
 help / color / mirror / Atom feed
From: "jdow" <jdow@earthlink.net>
To: "James Purser" <purserj@ksit.dynalias.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>
Cc: "Thomas Glanzmann" <sithglan@stud.uni-erlangen.de>,
	"LKML" <linux-kernel@vger.kernel.org>,
	"GIT" <git@vger.kernel.org>
Subject: Re: [PATCH] Really *do* nothing in while loop
Date: Sun, 8 May 2005 04:33:32 -0700	[thread overview]
Message-ID: <12e801c553c1$c454ea20$1225a8c0@kittycat> (raw)
In-Reply-To: 1115551204.3085.0.camel@kryten

From: "James Purser" <purserj@ksit.dynalias.com>

> On Sun, 2005-05-08 at 19:48, Michael Tokarev wrote:
> > Thomas Glanzmann wrote:
> > > [PATCH] Really *do* nothing in while loop
> > > 
> > > Signed-Off-by: Thomas Glanzmann <sithglan@stud.uni-erlangen.de>
> > > 
> > > --- a/sha1_file.c
> > > +++ b/sha1_file.c
> > > @@ -335,7 +335,7 @@
> > >  stream.next_in = hdr;
> > >  stream.avail_in = hdrlen;
> > >  while (deflate(&stream, 0) == Z_OK)
> > > - /* nothing */
> > > + /* nothing */;
> > >  
> > >  /* Then the data itself.. */
> > >  stream.next_in = buf;
> > 
> > Well, the lack of semicolon is wrong really (and funny).

You guys REALLY do not see the changed semantics here? You are
changing:
  while (deflate(&stream, 0) == Z_OK)
      stream.next_in = buf;

into

  while (deflate(&stream, 0) == Z_OK)
    ;
  /* Then the data itself.. */
  stream.next_in = buf;

I suspect the results of that tiny bit of code would be slightly
different, especially if "stream.next_in" is volatile, "buf"
is volatile, or if the assignment to next_in has an effect on
the "deflate" operation.

{^_^}




  reply	other threads:[~2005-05-08 11:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08  9:34 [PATCH] Really *do* nothing in while loop Thomas Glanzmann
2005-05-08  9:48 ` Michael Tokarev
2005-05-08 11:18   ` Thomas Glanzmann
2005-05-08 11:20   ` James Purser
2005-05-08 11:33     ` jdow [this message]
2005-05-08 11:40       ` Michael Tokarev
2005-05-08 21:08         ` Junio C Hamano
2005-05-08 21:16           ` Daniel Barkalow
2005-05-08 21:35             ` Junio C Hamano

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='12e801c553c1$c454ea20$1225a8c0@kittycat' \
    --to=jdow@earthlink.net \
    --cc=git@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjt@tls.msk.ru \
    --cc=purserj@ksit.dynalias.com \
    --cc=sithglan@stud.uni-erlangen.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