Re: [rfc] Autoselect x86_64 or i386 based on the remote g packet size

[Daniel Jacobowitz <drow@false.org>]

On Thu, Nov 09, 2006 at 04:49:24PM -0500, Daniel Jacobowitz wrote:
> Honestly, this clever auto-detection is much more useful for MIPS than
> it is for i386/AMD64; for MIPS, an executable file doesn't necessarily
> contain the answer to the question, but for i386 it always does.  I
> implemented the AMD64 bits after I had it working for MIPS, as a demo
> when Jan K. posted an even kludgier patch to warn about this case a
> couple of weeks ago.  If you don't like this bit, I'd be happy to drop
> it, and make gdbserver report the architecture manually when I advance
> to the XML stage of these target descriptions.  I won't mourn the i386
> parts of this patch.  Would you rather I did that?
> 
> (I'd like to hold on to the MIPS bits, because they're solving a
> slightly different problem, and because I know they're useful with
> existing non-gdbserver stubs that would be harder to fix.)

Hi Mark,

For avoidance of doubt, I'm definitely dropping the i386/amd64 patch.
It was a stretch to begin with.  I've already begun working on a patch
to specifiy the architecture explicitly and I really hope I'll have it
finished this week (but the way this entire project's been dragging
out, I'm not sure...).

Could you let me know if using the g packet size approach for the
clearer-cut MIPS situation is OK with you?  The difference, in my
opinion, is that it doesn't reflect a change in architecture; you can
run the same o32 ABI program on a 32-bit or 64-bit system, so it would
be nice if GDB could handle 32-bit or 64-bit regsets automatically.
This prevents a mips64 gdbserver having to figure out the child's ABI.

-- 
Daniel Jacobowitz
CodeSourcery