From: David Laight <David.Laight@ACULAB.COM>
To: 'Ammar Faizi' <ammarfaizi2@gnuweeb.org>,
Zhangjin Wu <falcon@tinylab.org>, Willy Tarreau <w@1wt.eu>
Cc: "Arnd Bergmann" <arnd@arndb.de>,
"Thomas Weißschuh" <thomas@t-8ch.de>,
"Yuan Tan" <tanyuan@tinylab.org>,
"Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>,
"Linux Kselftest Mailing List" <linux-kselftest@vger.kernel.org>
Subject: RE: [RFC] tools/nolibc: replace duplicated -ENOSYS return with single -ENOSYS return
Date: Wed, 30 Aug 2023 16:21:02 +0000 [thread overview]
Message-ID: <2d52dbd55e6240d5a91ebdce67fe0b7b@AcuMS.aculab.com> (raw)
In-Reply-To: <6f93ea82-f157-e921-2028-5b4fae4ad341@gnuweeb.org>
From: Ammar Faizi
> Sent: 30 August 2023 15:41
>
> On 8/28/23 4:51 AM, David Laight wrote:
> > I just found a(nother) clang bug:
> > int f(void) { return "a"[2]; }
> > compiles to just a 'return'.
>
> I don't think that's a bug. It's undefined behavior due to an
> out-of-bound read. What do you expect it to return?
I was actually expecting a warning/error if it didn't just read
the byte after the end of the string.
Just silently doing nothing didn't seem right for a modern compiler.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2023-08-30 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-27 8:32 [RFC] tools/nolibc: replace duplicated -ENOSYS return with single -ENOSYS return Zhangjin Wu
2023-08-27 9:17 ` Thomas Weißschuh
2023-08-29 6:29 ` Willy Tarreau
2023-08-30 0:19 ` Zhangjin Wu
2023-08-30 3:25 ` Willy Tarreau
2023-09-01 19:03 ` Zhangjin Wu
2023-09-03 9:31 ` Willy Tarreau
2023-08-27 21:51 ` David Laight
2023-08-28 9:46 ` David Laight
2023-08-29 23:39 ` Zhangjin Wu
2023-08-30 14:40 ` Ammar Faizi
2023-08-30 16:21 ` David Laight [this message]
2023-08-31 7:41 ` Zhangjin Wu
2023-08-31 8:37 ` David Laight
2023-09-01 19:48 ` Zhangjin Wu
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=2d52dbd55e6240d5a91ebdce67fe0b7b@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=ammarfaizi2@gnuweeb.org \
--cc=arnd@arndb.de \
--cc=falcon@tinylab.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=tanyuan@tinylab.org \
--cc=thomas@t-8ch.de \
--cc=w@1wt.eu \
/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.