This is the mail archive of the gdb-patches@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]

Helper functions in findvar.c predict current_gdbarch

From: Markus Deuling <deuling at de dot ibm dot com>
To: GDB Patches <gdb-patches at sourceware dot org>
Date: Wed, 16 Jan 2008 08:56:24 +0100
Subject: Helper functions in findvar.c predict current_gdbarch

Hi,

I noticed there are some "helper functions" in findvar.c predicated upon current_gdbarch (to find out the endianess etc.).
Those helper funtions are referred to pretty often:

findvar.c
extract_signed_integer          48
extract_unsigned_integer        350
extract_long_unsigned_integer   3
extract_typed_address           32
store_signed_integer            19
store_unsigned_integer          194
store_typed_address             7


Before I now begin to add "gdbarch as parameter" to all of those functions and to update their caller in the source >>> :-( <<< I just wanted
to ask you what you think would be the best way to get rid of current_gdbarch in those functions.

I hope you have better ideas than I have :-)

Regards,
Markus

--
 Markus Deuling
 GNU Toolchain for Linux on Cell BE
 deuling@de.ibm.com

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