gengtype.c (adjust_field_type): Diagnose duplicate "length" option applications and option being applied to...
gcc: 2012-07-27 Laurynas Biveinis <laurynas.biveinis@gmail.com> Steven Bosscher <steven@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.biveinis@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.biveinis@gmail.com> * include/line-map.h (line_map_macro): Use the "atomic" GTY option for the macro_locations field. Co-Authored-By: Steven Bosscher <steven@gcc.gnu.org> From-SVN: r189951
This commit is contained in:
committed by
Laurynas Biveinis
parent
1c5f95e6ec
commit
c0fd34971d
@@ -165,7 +165,7 @@ struct GTY(()) line_map_macro {
|
||||
In the example above x1 (for token "+") is going to be the same
|
||||
as y1. x0 is the spelling location for the argument token "1",
|
||||
and x2 is the spelling location for the argument token "2". */
|
||||
source_location * GTY((length ("2 * %h.n_tokens"))) macro_locations;
|
||||
source_location * GTY((atomic)) macro_locations;
|
||||
|
||||
/* This is the location of the expansion point of the current macro
|
||||
map. It's the location of the macro name. That location is held
|
||||
|
||||
Reference in New Issue
Block a user