Re: patch to gdb on Tru64 5.1

[Andrew Cagney <ac131313@cygnus.com>]

>> In the above, half of core_reg_mapping[] is determined by the macro
>> NFC_REGS.
>> 
>> Can you instead define both tables and select the correct one at
>> runtime?
> 
> 
> I don't understand your suggestion. The conditionalization is needed in
> order to successfully compile on Tru64 5.1. If I had 2 tables, one of
> them would not compile.

I've two requests:

	o	per NickD's post, could the table be initialised
		as either two separate entries, a single simple
		table.  Not something that is split down the middle
		by a #if/#else/#endif

	o	is it possible to compile in both tables
		so that the correct table can be selected
		at run time.  In theory allowing GDB to
		handle both 4.x and 5.x core files.

It sounds like the second one isn't going to fly.

To give some background to my second request, GDB is moving away from 
the good old days where it was always built/configured for a very 
specific host/target combination. Depending on that combination, certain 
features would, or would not be available.  For instance, 
shared-library, thread and core file support were all once native-only. 
  For an increasing number of targets, that is no longer the case.

	enjoy,
		Andrew