On Tue, 7 Feb 2017, Richard Biener wrote: > I'm not sure whether new RID_ keywords would be prefered for this > kind of stuff. We added one for __PHI. Joseph, is the RID_ space > somehow limited so that we should avoid ending up with, say, up to > 226 RID_s for GIMPLE (upper estimate taken from the number of > tree codes we have in tree.def)? I see currently cpplib puts > rid_code into an unsigned char and we do already seem to have quite > some of them (114 if I count correctly).
Apart from unsigned char, various places use 8-bit bit-fields for these values (the C and C++ parsers and c-indentation.h, at least). If necessary there would probably be scope for expanding those bit-fields without making tokens take more space, but I'm not sure about finding such space in cpp_hashnode and of course you'd need to find everywhere that uses unsigned char or a <= 8-bit bit-field for this. -- Joseph S. Myers jos...@codesourcery.com
