This is the mail archive of the gdb-cvs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

src/gdb dwarf2loc.c findvar.c valops.c ChangeLog


CVSROOT:	/cvs/src
Module name:	src
Changes by:	sagovic@sourceware.org	2013-08-29 12:25:04

Modified files:
	gdb            : dwarf2loc.c findvar.c valops.c ChangeLog 

Log message:
	cleanup: use value_lazy_at instead of allocate_value_lazy/attribute setter
	
	I came across a pattern used to construct a value in the following way:
	
	struct value *val = allocate_value_lazy (type);
	VALUE_LVAL (val) = lval_memory;
	set_value_address (val, address);
	
	Instead we fold the above call into:
	
	value_at_lazy (type, addr);
	
	2013-08-27  Sanimir Agovic  <sanimir.agovic@intel.com>
	
	* dwarf2loc.c (dwarf2_evaluate_loc_desc_full): Use value_at_lazy instead
	of assembling value via allocate_value_lazy and attribute setter.
	* findvar.c (default_read_var_value): Use value_at_lazy instead of
	assembling value via allocate_value_lazy and attribute setter.
	* valops.c (do_search_struct_field): Use value_at_lazy instead of
	assembling value via allocate_value_lazy and attribute setter.

Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/dwarf2loc.c.diff?cvsroot=src&r1=1.175&r2=1.176
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/findvar.c.diff?cvsroot=src&r1=1.151&r2=1.152
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/valops.c.diff?cvsroot=src&r1=1.316&r2=1.317
http://sourceware.org/cgi-bin/cvsweb.cgi/src/gdb/ChangeLog.diff?cvsroot=src&r1=1.15946&r2=1.15947


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]