https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109695
--- Comment #32 from rguenther at suse dot de <rguenther at suse dot de> --- On Tue, 9 May 2023, jakub at gcc dot gnu.org wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109695 > > --- Comment #29 from Jakub Jelinek <jakub at gcc dot gnu.org> --- > Comment on attachment 55031 > --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=55031 > WIP patch for a dynamic int_range<> > > What I meant is that by using a auto_vec could avoid reimplementing larger > chunks of vec.h/vec.cc for this. > Resizing by adding 10 more ranges can have higher compile time cost than what > vec.cc (calculate_allocation_1) does - doubles the size each time for smaller > sizes and and multiplying previous by 3 / 2 for larger ones. If we still have a hard limit on the MAX number of ranges (previosly 255) then I'd probably go straight from stack -> that MAX and never re-allocate further?
