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 10:02:40 +0100 [thread overview]
Message-ID: <20010124100240.A4526@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>
In-Reply-To: <20010123235115.A14786@twiddle.net>; from rth@twiddle.net on Tue, Jan 23, 2001 at 11:51:15PM -0800
On Tue, Jan 23, 2001 at 11:51:15PM -0800, Richard Henderson wrote:
> On Thu, Jan 11, 2001 at 12:59:24AM +0100, Andrea Arcangeli wrote:
> > What I said is that I can write this C code:
> >
> > int x[2], * p = (int *) (((char *) &x)+1);
> > main()
> > {
> > *p = 0;
> > }
> >
> > This is legal C code.
>
> Err, no. This is not "legal" by any stretch of the imagination.
> This code has undefined behaviour.
I know this code has undefined behaviour at _runtime_. But I thought
you were obliged to allow it to compile. That was my only point.
> We aren't even obliged to allow this to compile.
I'd love if you could forbid it to compile.
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 9:02 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 [this message]
2001-01-24 9:51 ` Richard Henderson
2001-01-24 12:21 ` Andrea Arcangeli
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=20010124100240.A4526@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