On Fri, Feb 02, 2007 at 02:31:55PM -0800, Christopher Li wrote: > On Fri, Feb 02, 2007 at 05:37:45PM -0500, Pavel Roskin wrote: > > > > /usr/include/sys/socket.h:88:62: error: attribute > > '__transparent_union__': ignoring attribute __transparent_union__ > > /usr/include/sys/socket.h:92:68: error: attribute > > '__transparent_union__': ignoring attribute __transparent_union__ > > /usr/include/netdb.h:661:60: error: typename in expression > > /usr/include/stdlib.h:72:56: error: attribute '__transparent_union__': > > ignoring attribute __transparent_union__ > > I see, that is because sparse does not handle attribute > __transparent_union__ yet. We should improve sparse instead of paper > cover the error message. I'm not sure. __transparent_union__ is an atrocious kludge and it does deserve a warning. So getting it to STFU on known offenders we have no chance to fix is OK, but legitimizing that abortion is not. > > /usr/include/regex.h:543:27: error: typename in expression > > Similar here, that is because gcc has this key word "restrict" > inside bracket. Sparse know nothing about "restrict". > > > I'm not going to fix socket.h. I'm checking my code, not glibc. > > Again, we should fix sparse instead. Unlike __transparent_union__, restrict is at least a valid C... It's not that hard to handle, except for the shortage of bits for modifiers... - 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
