On Fri, 12 Sep 2014 23:43:51 + "Rustad, Mark D"
wrote:
> Do you mean the number of warnings enabled, or the number of warning messages
> being generated?
The latter.
My problem is I use crufty old compilers so a number of the warnings I
see aren't seen by sane people and it' snot worth
Michal,
On Sep 12, 2014, at 4:37 PM, Michal Nazarewicz wrote:
> On Fri, Sep 12 2014, Andrew Morton wrote:
>> On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz
>> wrote:
>>
>>> Because min and max macros use the same variable names no matter
>>> how many times they are called (or how deep
On Sep 12, 2014, at 3:40 PM, Andrew Morton wrote:
> On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz
> wrote:
>
>> Because min and max macros use the same variable names no matter
>> how many times they are called (or how deep the nesting of their
>> calls), each time min or max calls are
On Fri, Sep 12 2014, Andrew Morton wrote:
> On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz
> wrote:
>
>> Because min and max macros use the same variable names no matter
>> how many times they are called (or how deep the nesting of their
>> calls), each time min or max calls are nested,
On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz wrote:
> Because min and max macros use the same variable names no matter
> how many times they are called (or how deep the nesting of their
> calls), each time min or max calls are nested, the same variables
> are declared. This is
On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz min...@mina86.com wrote:
Because min and max macros use the same variable names no matter
how many times they are called (or how deep the nesting of their
calls), each time min or max calls are nested, the same variables
are declared. This
On Fri, Sep 12 2014, Andrew Morton a...@linux-foundation.org wrote:
On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz min...@mina86.com
wrote:
Because min and max macros use the same variable names no matter
how many times they are called (or how deep the nesting of their
calls), each
On Sep 12, 2014, at 3:40 PM, Andrew Morton a...@linux-foundation.org wrote:
On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz min...@mina86.com
wrote:
Because min and max macros use the same variable names no matter
how many times they are called (or how deep the nesting of their
Michal,
On Sep 12, 2014, at 4:37 PM, Michal Nazarewicz min...@mina86.com wrote:
On Fri, Sep 12 2014, Andrew Morton a...@linux-foundation.org wrote:
On Thu, 11 Sep 2014 23:39:36 +0200 Michal Nazarewicz min...@mina86.com
wrote:
Because min and max macros use the same variable names no
On Fri, 12 Sep 2014 23:43:51 + Rustad, Mark D mark.d.rus...@intel.com
wrote:
Do you mean the number of warnings enabled, or the number of warning messages
being generated?
The latter.
My problem is I use crufty old compilers so a number of the warnings I
see aren't seen by sane people
Because min and max macros use the same variable names no matter
how many times they are called (or how deep the nesting of their
calls), each time min or max calls are nested, the same variables
are declared. This is especially noisy after min3 and max3 have
been changed to nest min/max calls.
Because min and max macros use the same variable names no matter
how many times they are called (or how deep the nesting of their
calls), each time min or max calls are nested, the same variables
are declared. This is especially noisy after min3 and max3 have
been changed to nest min/max calls.
12 matches
Mail list logo