FreeChainXenon/binutils-gdb
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

* c-exp.y (exp): Add production to support direct creation

Browse source 
of array constants using the obvious syntax.
	* c-valprint.c (c_val_print):  Set printed string length.
	* dwarfread.c (read_tag_string_type):  New prototype and
	function that handles TAG_string_type DIEs.
	* dwarfread.c (process_dies):  Add case for TAG_string_type
	that calls new read_tag_string_type function.
	* expprint.c (print_subexp):  Add support for OP_ARRAY.
	* gdbtypes.c (create_range_type, create_array_type):  Inherit
	objfile from the index type.
	**** start-sanitize-chill ****
	* ch-typeprint.c (chill_print_type):  Add case for
	TYPE_CODE_STRING.
	* ch-valprint.c (chill_val_print):  Fix case for
	TYPE_CODE_STRING.
	**** end-sanitize-chill ****
This commit is contained in:
Fred Fish 1993-01-19 23:00:19 +00:00
parent fa2b89f103
commit ec16f7015b
6 changed files with 95 additions and 13 deletions
Download patch file Download diff file Expand all files Collapse all files

14
gdb/gdbtypes.c
View file

@ -314,8 +314,10 @@ allocate_stub_method (type)
}
/* Create a range type using either a blank type supplied in RESULT_TYPE,
or creating a new type. Indices will be of type INDEX_TYPE, and will
range from LOW_BOUND to HIGH_BOUND, inclusive.
or creating a new type, inheriting the objfile from INDEX_TYPE.
Indices will be of type INDEX_TYPE, and will range from LOW_BOUND to
HIGH_BOUND, inclusive.
FIXME: Maybe we should check the TYPE_CODE of RESULT_TYPE to make
sure it is TYPE_CODE_UNDEF before we bash it into a range type? */
@ -348,8 +350,10 @@ create_range_type (result_type, index_type, low_bound, high_bound)
/* Create an array type using either a blank type supplied in RESULT_TYPE,
or creating a new type. Elements will be of type ELEMENT_TYPE, the
indices will be of type RANGE_TYPE.
or creating a new type, inheriting the objfile from RANGE_TYPE.
Elements will be of type ELEMENT_TYPE, the indices will be of type
RANGE_TYPE.
FIXME: Maybe we should check the TYPE_CODE of RESULT_TYPE to make
sure it is TYPE_CODE_UNDEF before we bash it into an array type? */
@ -374,7 +378,7 @@ create_array_type (result_type, element_type, range_type)
}
if (result_type == NULL)
{
result_type = alloc_type (TYPE_OBJFILE (element_type));
result_type = alloc_type (TYPE_OBJFILE (range_type));
}
TYPE_CODE (result_type) = TYPE_CODE_ARRAY;
TYPE_TARGET_TYPE (result_type) = element_type;