Re: [PATCH v19 02/40] c-family, c++: Look up built-in traits through gperf

On Sun, Oct 15, 2023 at 2:50 PM Patrick Palka wrote: > > On Sun, 15 Oct 2023, Ken Matsui wrote: > > > On Sun, Oct 15, 2023 at 1:43 PM Patrick Palka wrote: > > > > > > On Fri, 13 Oct 2023, Ken Matsui wrote: > > > > > > > Since RID_MAX soon reaches 255 and all built-in traits are used > > > >

Re: [PATCH v19 02/40] c-family, c++: Look up built-in traits through gperf

On Sun, 15 Oct 2023, Ken Matsui wrote: > On Sun, Oct 15, 2023 at 1:43 PM Patrick Palka wrote: > > > > On Fri, 13 Oct 2023, Ken Matsui wrote: > > > > > Since RID_MAX soon reaches 255 and all built-in traits are used > > > approximately > > > once in a C++ translation unit, this patch removes all

Re: [PATCH v19 02/40] c-family, c++: Look up built-in traits through gperf

On Sun, Oct 15, 2023 at 1:43 PM Patrick Palka wrote: > > On Fri, 13 Oct 2023, Ken Matsui wrote: > > > Since RID_MAX soon reaches 255 and all built-in traits are used > > approximately > > once in a C++ translation unit, this patch removes all RID values for > > built-in > > traits and uses

Re: [PATCH v19 02/40] c-family, c++: Look up built-in traits through gperf

On Fri, 13 Oct 2023, Ken Matsui wrote: > Since RID_MAX soon reaches 255 and all built-in traits are used approximately > once in a C++ translation unit, this patch removes all RID values for built-in > traits and uses gperf to look up the specific trait. Rather than holding > traits as keywords,

[PATCH v19 02/40] c-family, c++: Look up built-in traits through gperf

Since RID_MAX soon reaches 255 and all built-in traits are used approximately once in a C++ translation unit, this patch removes all RID values for built-in traits and uses gperf to look up the specific trait. Rather than holding traits as keywords, we set all trait identifiers as cik_trait,