[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75VfEVhx30=GRLDBQDjkevepgTcqYRTVrafeTsepKsZ3ctw@mail.gmail.com>
Date: Sat, 23 Nov 2024 20:31:52 +0200
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: David Laight <David.Laight@...lab.com>
Cc: Mateusz Guzik <mjguzik@...il.com>, "tglx@...utronix.de" <tglx@...utronix.de>, "bp@...en8.de" <bp@...en8.de>,
"andy@...nel.org" <andy@...nel.org>, "akpm@...ux-foundation.org" <akpm@...ux-foundation.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "x86@...nel.org" <x86@...nel.org>,
Nathan Chancellor <nathan@...nel.org>
Subject: Re: [PATCH 2/2] string: retire bcmp()
On Sat, Nov 23, 2024 at 5:13 PM David Laight <David.Laight@...lab.com> wrote:
> From: Mateusz Guzik
> > Sent: 23 November 2024 09:47
...
> > -/*
> > - * Clang may lower `memcmp == 0` to `bcmp == 0`.
> > - */
> As per the comment I thought that clang would sometimes generate
> calls to bcmp().
>
> So while the two symbols could refer to the same code I don't
> think it can be removed.
You beat me to it, I came just to say the same thing.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists