>>>> Even though clustered_apic_mode is 0, the compiler still complains
>>>> about the second one and the first one doesn't depend on
>>>> clustered_apic_mode at all.
>>>>
>>> Hmmm ... not sure why the compiler complains about the second one,
>>> that's very strange ;-)
>>>
>>
>> I agree. The cpp ouput clealy shows
>>
>> if ((0) && (numnodes > 1)) {
>>
>> so I'm not sure why there's a problem.
>
> Is the thing generating the "(0)" a macro? If so, then the rules
#define clustered_apic_mode (0)
> of C and the "&&" operator say that "if the first is false, the
> second needn't even be evaluated".
That's what I would have thought.
But I don't think it's the second part that causes the warning,
it's the thing *inside* the if clause.
> Could that be what's causing the warning?
To my mind, that's why we should *not* be getting a warning ?
M.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Apr 23 2002 - 22:00:19 EST