This is the mail archive of the gdb@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] |
On Wed, Apr 01, 2009 at 10:15:33PM +0200, Jonas Maebe wrote:Which brings me to the next point: how does one go about "allocating" a
new DW_AT_calling_convention value in the DW_CC_lo_user .. DW_CC_hi_user
range? At first sight, there is only one such value currently in public
use (DW_CC_GNU_renesas_sh). Can I just take 0x41 for
DW_CC_BORLAND_fastcall_i386? And should I then submit this constant for
inclusion in binutils first?
I don't know - might want to raise this on the DWARF discussion list (see dwarfstd.org).
I would like to use a new DW_AT_calling_convention attribute value in the range DW_CC_lo_user .. DW_CC_hi_user. As far as I can tell, the only one currently in (public) use is DW_CC_GNU_renesas_sh (= 0x40). My question is: how does one go about reserving/obtaining such a number? Do you just take the next one that appears to be available and submit patches using this value to binutils (for elf/dwarf.h) and gdb? (and possibly dwarflib, and maybe others)
The DWARF committee decides on the common uses in the <lo_user range. It's entirely reasonable to propose new values in the common range.
Thanks, Roland
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |