All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Jackson <pj@sgi.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [samuel.thibault@ens-lyon.org: Re: warning: comparison is always false due to limited range of  data type]
Date: Wed, 18 Aug 2004 17:50:03 -0700	[thread overview]
Message-ID: <20040818175003.1d1671bb.pj@sgi.com> (raw)
In-Reply-To: <20040818230211.GG22559@bouh.is-a-geek.org>

Samuel wrote:
> Here is another approach. This should never warning, and should get
> optimized away as needed.

Yours looks like it has a better chance of not being broken by some
future gcc enhancement that can see through the obfuscation in mine.

I didn't actually try it, but yours looks good to me.

Thanks.

-- 
                          I won't rest till it's the best ...
                          Programmer, Linux Scalability
                          Paul Jackson <pj@sgi.com> 1.650.933.1373

      reply	other threads:[~2004-08-19  0:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-18 23:02 [samuel.thibault@ens-lyon.org: Re: warning: comparison is always false due to limited range of data type] Samuel Thibault
2004-08-19  0:50 ` Paul Jackson [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

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

  git send-email \
    --in-reply-to=20040818175003.1d1671bb.pj@sgi.com \
    --to=pj@sgi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=samuel.thibault@ens-lyon.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.