From: David Laight <David.Laight@ACULAB.COM>
To: 'Kent Overstreet' <kent.overstreet@linux.dev>,
"Russell King (Oracle)" <linux@armlinux.org.uk>
Cc: Arnd Bergmann <arnd@arndb.de>,
Calvin Owens <jcalvinowens@gmail.com>,
"Dave Martin" <Dave.Martin@arm.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-bcachefs@vger.kernel.org" <linux-bcachefs@vger.kernel.org>
Subject: RE: [PATCH] arm: Silence gcc warnings about arch ABI drift
Date: Mon, 19 Feb 2024 19:53:15 +0000 [thread overview]
Message-ID: <ff0164553d6f486f97643eae8235cc5f@AcuMS.aculab.com> (raw)
In-Reply-To: <fharyfc7fnh45dthgd2ehwsgdqzmdfptp7jw7gi5ahb6slwgf6@nrkhlhvbbzx7>
...
> I'm not always trying to write code that will generate the fastest
> assembly possible; there aro other considerations. As long a the
> compiler is doing something /reasonable/, the code is fine.
Speaks the man who was writing horrid 'jit' code ...
This also begs the question of why that data is so compressed
in the first place?
It is quite likely that a few accesses generate far more code
than the data you are attempting to save.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-19 19:53 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-19 4:09 [PATCH] arm: Silence gcc warnings about arch ABI drift Calvin Owens
2024-02-19 6:21 ` Arnd Bergmann
2024-02-19 6:25 ` Kent Overstreet
2024-02-19 7:56 ` Arnd Bergmann
2024-02-19 6:58 ` Calvin Owens
2024-02-19 7:03 ` Kent Overstreet
2024-02-19 9:26 ` Russell King (Oracle)
2024-02-19 9:40 ` Kent Overstreet
2024-02-19 9:52 ` Russell King (Oracle)
2024-02-19 9:56 ` Kent Overstreet
2024-02-19 19:53 ` David Laight [this message]
2024-02-19 21:38 ` Kent Overstreet
2024-02-19 22:04 ` David Laight
2024-02-19 9:57 ` Arnd Bergmann
2024-02-19 10:08 ` Kent Overstreet
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=ff0164553d6f486f97643eae8235cc5f@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=Dave.Martin@arm.com \
--cc=arnd@arndb.de \
--cc=jcalvinowens@gmail.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
/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;
as well as URLs for NNTP newsgroup(s).