On Sat, Feb 1, 2014 at 10:49 AM, Josh Triplett <josh@xxxxxxxxxxxxxxxx> wrote:
> Commit 3829c4d8b097776e6b3472290a9fae08a705ab7a ("Don't mix storage
> class bits with ctype->modifiers while parsing type") in 2009 separated
> storage classes from modifiers; in the process, it changed
> __attribute__((force)) from a modifier to a storage class. I don't
> think it makes sense to have force as a storage class, for one critical
> reason: storage classes are mutually exclusive.
I am not convinced yet.
The current usage case for attribute "force" is to silence the type
mismatch during the type conversion. For variable declaration, there is
not need to silence any mismatch because there is no type conversion.
What you are purposing here is a new usage case. Do you want
to silence every single type mismatch in every assignment to that
variable? How about assignment from that variable?
That seems a lot of complexity to keep track of the attribute
belong to which level of the type tree.
>
> $ cat /tmp/test.c
> static __attribute__((force)) int *p;
> static int q = *p;
In this example, the attribute "force" is not needed.
I think it compiles fine without forcing it. The "force" don't
actually do any thing. So why do we want to support this?
I want to justify the extra complexity it add to the code
base.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
