On Fri, Jul 27, 2012 at 2:59 PM, Laurynas Biveinis <laurynas.bivei...@gmail.com> wrote: > This is a slightly expanded version of the patch in [1]. The main difference > is that I expanded gengtype diagnostics to error on GTY length option applied > to strings too, in addition to other arrays of atomic types. This in turn > uncovered another place where a correct GTY option should be used . > > Java and libcpp parts are already approved. > > Tested on x86_64 linux, no regressions. OK for trunk?
Ok. Thanks, Richard. > [1] http://gcc.gnu.org/ml/gcc-patches/2012-07/msg01204.html > > gcc: > 2012-07-27 Laurynas Biveinis <laurynas.bivei...@gmail.com> > Steven Bosscher <ste...@gcc.gnu.org> > > * gengtype.c (adjust_field_type): Diagnose duplicate "length" > option applications and option being applied to arrays of atomic > types. > (walk_type): Allow "atomic" option on strings too. > * dwarf2out.h (struct dw_vec_struct): Use the "atomic" GTY option > for the array field. > * vec.h: Describe the atomic object "A" type of the macros in > the header comment. > (VEC_T_GTY_ATOMIC, DEF_VEC_A, DEF_VEC_ALLOC_A): Define. > * emit-rtl.c (locations_locators_vals): use the atomic object > vector. > * doc/gty.texi: Clarify that GTY option "length" is only for > arrays of non-atomic objects. Fix typo in the description of the > "atomic" option. > > gcc/java: > 2012-07-24 Laurynas Biveinis <laurynas.bivei...@gmail.com> > > * jcf.h (CPool): Use the "atomic" GTY option for the tags field. > (bootstrap_method): Likewise for the bootstrap_arguments field. > > libcpp: > 2012-07-24 Laurynas Biveinis <laurynas.bivei...@gmail.com> > > * include/line-map.h (line_map_macro): Use the "atomic" GTY option > for the macro_locations field. > > > -- > Laurynas
