[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <c479e2727e4e49739d86b8e2b0b0a221@AcuMS.aculab.com>
Date: Mon, 19 Feb 2024 22:04:20 +0000
From: David Laight <David.Laight@...LAB.COM>
To: 'Kent Overstreet' <kent.overstreet@...ux.dev>
CC: "Russell King (Oracle)" <linux@...linux.org.uk>, Arnd Bergmann
<arnd@...db.de>, Calvin Owens <jcalvinowens@...il.com>, Dave Martin
<Dave.Martin@....com>, "linux-arm-kernel@...ts.infradead.org"
<linux-arm-kernel@...ts.infradead.org>, "linux-kernel@...r.kernel.org"
<linux-kernel@...r.kernel.org>, "linux-bcachefs@...r.kernel.org"
<linux-bcachefs@...r.kernel.org>
Subject: RE: [PATCH] arm: Silence gcc warnings about arch ABI drift
From: Kent Overstreet
> Sent: 19 February 2024 21:38
>
> On Mon, Feb 19, 2024 at 07:53:15PM +0000, David Laight wrote:
> > ...
> > > 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.
>
> It's easy to understand if you understand profiling, benchmarking and
> cache effects.
And how arguments get passed to functions :-)
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
Powered by blists - more mailing lists