On Thu, Jun 07, 2018 at 09:25:09PM +0200, Rasmus Villemoes wrote: > > IIRC, the problem is that sparse pretends to be the gcc sparse itself > was built with, which is obviously entirely unrelated to the C dialect > that that particular sparse version groks. Sigh. Ack to the fix above.
Yes, indeed, and it is sometimes a problem. Ideal would be that sparse would pretend to be same GCC as the one used to compile the code being checked *and* to have exactly the same features. Pretending to be an older version of GCC would maybe solve the present problem it's not really a general solution. One good thing would be to not depend on GCC versions to enable some features (but GCC offers few facilities helping here). Best regards, -- Luc Van Oostenryck
