dist/gdb/ada-lang.c

344      accessible through a component ("tsd") in the object tag.  But this
2614 value_assign_to_component (struct value *container, struct value *component,
2618     (LONGEST)  (value_address (component) - value_address (container));
2620     value_bitpos (component) - value_bitpos (container);
2623   val = value_cast (value_type (component), val);
2625   if (value_bitsize (component) == 0)
2626     bits = TARGET_CHAR_BIT * TYPE_LENGTH (value_type (component));
2628     bits = value_bitsize (component);
2634       if (is_scalar_type (check_typedef (value_type (component))))
2636 	  = TYPE_LENGTH (value_type (component)) * TARGET_CHAR_BIT - bits;
4256    structure/union, extract the component named NAME from the ultimate
4376     error (_("Attempt to extract a component of "
4434       struct value *component = ada_value_struct_elt (aligner, "F", 0);
4436       value_assign_to_component (aligner, component, actual);
6947    component to print and there's no issue but in this particular
6950    component C from the Middle_T view, but also component C from
6951    Bottom_T.  So in that "undefined" case, when the component is
7235 /* Given a type TYPE, look up the type of the component of type named NAME.
7365       error (_("Type %s has no component named %s"),
9430 /* Total number of component associations in the aggregate starting at
9459    component of LHS (a simple array or a record), updating *POS past
9582 /* Assign into the component of LHS indexed by the OP_POSITIONAL
9664 	      error (_("Invalid record component association."));
9670 	    error (_("Unknown component name: %s."), name);
9675 	error (_("Index in component association out of bounds."));
9954     However, if a component does not have a dynamic size, the component
9971     In that example, the compiler creates a PAD type for component First,
9972     whose size is constant, and then positions the component After just
9973     right after it.  The offset of component After is therefore constant
9988     the component name).  Even if the target type is a PAD type, the size
9991     we might end up with the wrong size for our component.  This can be
10013     when selecting one component of a record, this specific component
10015     of a record, each component should be fixed before its value gets
10351 		 We use the type name of the "_parent" component in order
10353 		 If that component had a dynamic size, the resolution into
11126 		     "component association: %s."), &exp->elts[pc+2].string);