Re: [PATCH next v2 11/11] minmax: min() and max() don't need to return constant expressions

2024-02-26 Thread kernel test robot
v2 11/11] minmax: min() and max() don't need to return constant expressions config: i386-randconfig-011-20240226 (https://download.01.org/0day-ci/archive/20240226/202402261802.9shoxrwy-...@intel.com/config) compiler: gcc-12 (Debian 12.2.0-14) 12.2.0 reproduce (this is a W=1 build): (https

RE: [PATCH next v2 11/11] minmax: min() and max() don't need to return constant expressions

2024-02-26 Thread David Laight
From: kernel test robot > Sent: 26 February 2024 09:42 > If you fix the issue in a separate patch/commit (i.e. not just a new version > of > the same patch/commit), kindly add following tags > | Reported-by: kernel test robot > | Closes: >

Re: [PATCH next v2 11/11] minmax: min() and max() don't need to return constant expressions

2024-02-26 Thread kernel test robot
v2 11/11] minmax: min() and max() don't need to return constant expressions config: i386-buildonly-randconfig-001-20240226 (https://download.01.org/0day-ci/archive/20240226/202402261720.eamc0ehm-...@intel.com/config) compiler: clang version 17.0.6 (https://github.com/llvm/llvm-project

[PATCH next v2 11/11] minmax: min() and max() don't need to return constant expressions

2024-02-25 Thread David Laight
After changing the handful of places max() was used to size an on-stack array to use max_const() it is no longer necessary for min() and max() to return constant expressions from constant inputs. Remove the associated logic to reduce the expanded text. Remove the 'hack' that allowed max(bool,