From: Andrea Arcangeli <andrea@suse.de>
To: Richard Henderson <rth@twiddle.net>
Cc: Russell King <rmk@arm.linux.org.uk>,
Hubert Mantel <mantel@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: Compatibility issue with 2.2.19pre7
Date: Wed, 24 Jan 2001 13:21:44 +0100 [thread overview]
Message-ID: <20010124132144.A13308@athlon.random> (raw)
In-Reply-To: <20010110163158.F19503@athlon.random> <200101102209.f0AM9N803486@flint.arm.linux.org.uk> <20010111005924.L29093@athlon.random> <20010123235115.A14786@twiddle.net> <20010124100240.A4526@athlon.random> <20010124015149.A14891@twiddle.net>
In-Reply-To: <20010124015149.A14891@twiddle.net>; from rth@twiddle.net on Wed, Jan 24, 2001 at 01:51:49AM -0800
On Wed, Jan 24, 2001 at 01:51:49AM -0800, Richard Henderson wrote:
> On Wed, Jan 24, 2001 at 10:02:40AM +0100, Andrea Arcangeli wrote:
> > I'd love if you could forbid it to compile.
>
> Problem is that there's stuff like this all over the place. Plus,
That's why I thought you were required to make it to compile. For example
you don't know if there's another object that will cast the int pointer back to
char pointer before dereferencing. That would get a defined runtime behaviour
on all archs.
And yes, I see above I'm not allowed to say "runtime" nor "defined behaviour"
according to the standard, but that's how thing works in practice.
Andrea
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-24 12:21 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 0:37 Compatibility issue with 2.2.19pre7 Hubert Mantel
2001-01-10 0:43 ` Alan Cox
2001-01-10 6:54 ` Russell King
2001-01-10 15:31 ` Andrea Arcangeli
2001-01-10 22:09 ` Russell King
2001-01-10 23:59 ` Andrea Arcangeli
2001-01-11 7:34 ` Russell King
2001-01-11 10:33 ` Andi Kleen
2001-01-11 10:36 ` Russell King
2001-01-11 12:10 ` Manfred
2001-01-11 12:10 ` Andi Kleen
2001-01-11 12:29 ` Manfred
2001-01-11 13:27 ` Russell King
2001-01-24 7:51 ` Richard Henderson
2001-01-24 9:02 ` Andrea Arcangeli
2001-01-24 9:51 ` Richard Henderson
2001-01-24 12:21 ` Andrea Arcangeli [this message]
2001-01-24 17:49 ` Richard Henderson
2001-01-24 10:09 ` Thomas Pornin
2001-01-11 15:28 ` Trond Myklebust
2001-01-11 16:19 ` Manfred Spraul
2001-01-11 17:44 ` Trond Myklebust
2001-01-11 18:22 ` Trond Myklebust
2001-01-11 18:27 ` Andrea Arcangeli
2001-01-11 18:30 ` Trond Myklebust
2001-01-11 18:43 ` Andrea Arcangeli
2001-01-11 20:09 ` Russell King
2001-01-11 20:39 ` Trond Myklebust
2001-01-11 11:37 ` Trond Myklebust
-- strict thread matches above, loose matches on Subject: below --
2001-01-24 13:46 Jesse Pollard
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=20010124132144.A13308@athlon.random \
--to=andrea@suse.de \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=mantel@suse.de \
--cc=rmk@arm.linux.org.uk \
--cc=rth@twiddle.net \
/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