From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yury Norov Date: Fri, 01 Jul 2022 02:58:11 +0000 Subject: Re: [PATCH v5 0/9] bitops: let optimize out non-atomic bitops on compile-time constants Message-Id: List-Id: References: <20220624121313.2382500-1-alexandr.lobakin@intel.com> <20220630165611.1551808-1-alexandr.lobakin@intel.com> In-Reply-To: <20220630165611.1551808-1-alexandr.lobakin@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Alexander Lobakin Cc: Arnd Bergmann , Andy Shevchenko , Mark Rutland , Matt Turner , Brian Cain , Geert Uytterhoeven , Yoshinori Sato , Rich Felker , "David S. Miller" , Kees Cook , "Peter Zijlstra (Intel)" , Marco Elver , Borislav Petkov , Tony Luck , Maciej Fijalkowski , Jesse Brandeburg , Greg Kroah-Hartman , Nathan Chancellor , Nick Desaulniers , Tom Rix , kernel test robot , linux-alpha@vger.kernel.org, linux-hexagon@vger.kernel.org, linux-ia64@vger.kernel.org, linux-m68k@lists.linux-m68k.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-arch@vger.kernel.org, llvm@lists.linux.dev, linux-kernel@vger.kernel.org On Thu, Jun 30, 2022 at 06:56:11PM +0200, Alexander Lobakin wrote: > From: Alexander Lobakin > Date: Fri, 24 Jun 2022 14:13:04 +0200 > > > While I was working on converting some structure fields from a fixed > > type to a bitmap, I started observing code size increase not only in > > places where the code works with the converted structure fields, but > > also where the converted vars were on the stack. That said, the > > following code: > > Hey, > > Seems like everything is fine this time. I got some reports, but > those aren't caused by any of the changes from the series. > Maybe we can take it to -next and see how it goes? Applied on github.com:/norov/linux.git branch bitmap-for-next Thanks!