All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	"Richard B. Johnson" <root@chaos.analogic.com>,
	Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (7/13): gcc 3.3 adaptions.
Date: Mon, 24 Feb 2003 17:39:34 -0500	[thread overview]
Message-ID: <20030224173934.T3910@devserv.devel.redhat.com> (raw)
In-Reply-To: <jeznol5plv.fsf@sykes.suse.de>; from schwab@suse.de on Mon, Feb 24, 2003 at 10:35:24PM +0100

On Mon, Feb 24, 2003 at 10:35:24PM +0100, Andreas Schwab wrote:
> Linus Torvalds <torvalds@transmeta.com> writes:
> 
> |> Does gcc still warn about things like
> |> 
> |> 	#define COUNT (sizeof(array)/sizeof(element))
> |> 
> |> 	int i;
> |> 	for (i = 0; i < COUNT; i++)
> |> 		...
> |> 
> |> where COUNT is obviously unsigned (because sizeof is size_t and thus 
> |> unsigned)?
> |> 
> |> Gcc used to complain about things like that, which is a FUCKING DISASTER. 
> 
> How can you distinguish that from other occurrences of (int)<(size_t)?

Value range propagation pass, then warn?

	Jakub

  parent reply	other threads:[~2003-02-24 22:29 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-24 18:10 [PATCH] s390 (7/13): gcc 3.3 adaptions Martin Schwidefsky
2003-02-24 19:44 ` Richard B. Johnson
2003-02-24 21:02   ` Linus Torvalds
2003-02-24 21:27     ` Jeff Garzik
2003-02-24 21:33     ` Richard B. Johnson
2003-02-24 21:35     ` Andreas Schwab
2003-02-24 21:53       ` Jeff Garzik
2003-02-24 22:07         ` Andreas Schwab
2003-02-24 22:21           ` Jörn Engel
2003-02-24 22:31             ` Jörn Engel
2003-02-25 12:34             ` Andreas Schwab
2003-02-24 22:39           ` Linus Torvalds
2003-02-25  0:20             ` Alan Cox
2003-02-24 23:20               ` Linus Torvalds
2003-02-25  0:40                 ` Alan Cox
2003-02-24 23:51                   ` Linus Torvalds
2003-02-25  5:24             ` Chris Wedgwood
2003-02-25 12:25               ` Jamie Lokier
2003-02-25 12:40             ` Andreas Schwab
2003-02-25 15:27               ` Linus Torvalds
2003-02-25 15:39                 ` Andreas Schwab
2003-02-25 16:02                   ` Linus Torvalds
2003-02-25 16:15                     ` Linus Torvalds
2003-02-25 16:26                     ` Andreas Schwab
2003-02-25 16:17                 ` Richard B. Johnson
2003-02-24 22:28       ` Linus Torvalds
2003-02-24 22:39       ` Jakub Jelinek [this message]
2003-02-24 23:52         ` John Alvord
2003-02-24 21:38     ` Adrian Bunk
2003-03-01  3:12     ` Richard Henderson
     [not found] <20030224195008$59ef@gated-at.bofh.it>
     [not found] ` <20030224195008$40bd@gated-at.bofh.it>
2003-02-24 20:03   ` Arnd Bergmann
2003-02-24 20:49     ` Richard B. Johnson

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=20030224173934.T3910@devserv.devel.redhat.com \
    --to=jakub@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=root@chaos.analogic.com \
    --cc=schwab@suse.de \
    --cc=schwidefsky@de.ibm.com \
    --cc=torvalds@transmeta.com \
    /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.