On Wed, Nov 27, 2019 at 12:21:01AM +0000, Ramsay Jones wrote: > > > On 26/11/2019 20:30, Luc Van Oostenryck wrote: > > Sparse knows about __int128_t, __uint128_t & __int128. > > > > However, internally, these types are treated as a kind of 128-bit > > 'long long long' type. It's mainly a question of variable naming, > > but these types are also displayed by show_typename() as > > 'long long long' which can't be parsed back, neither by GCC, > > nor even by sparse itself. > > > > So, rename the variables to use 'int128' and let show_typename() > > display these types as '[signed|unsigned] __int128'. > > > > Reported-by: Ramsay Jones <ramsay@xxxxxxxxxxxxxxxxxxxx> > > Signed-off-by: Luc Van Oostenryck <luc.vanoostenryck@xxxxxxxxx> > > Hmm, where does this patch apply? I tried 'master' along with > (on a hunch) 'luc/parse-spec', but could not get it to 'git-am' > correctly. Mmmm, yes, sorry for that. It probably only apply on top of the merge of the pending branches, including the one with all the other 'arch cleaning' patches which I still need to check after some changes and new patches. I've pushed everything now on github: git://github.com/lucvoo/sparse-dev.git int128_ctype and I think it look pretty good (at least for the 12-15 arch/bitness combo that I'm tracking). Best regards, -- Luc
