On 23/07/18 00:39, Luc Van Oostenryck wrote: [snip] > I had few time today to think about it but think there are only > two possible solutions: > 1) add the needed typing at instruction level > 2) at some point (probably during linearization itself) decide > that for now shift counts will be interpreted as some fixed > type (for example signed or unsigned int, because larger types > are rarely used for shift counts). Yeah, my initial thought was to just use an int; it should be good enough for any reasonable value, after all. However, if you want to provide behaviour similar to gcc, then I guess you need to find some way to add the type of the shift argument to the instruction (or the pseudo src2, I guess). ATB, Ramsay Jones -- 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
