This is the mail archive of the
binutils@sourceware.cygnus.com
mailing list for the binutils project.
Re: Default architecture according --target=...configury?
- To: Ian Lance Taylor <ian@zembu.com>
- Subject: Re: Default architecture according --target=...configury?
- From: Andrew Cagney <ac131313@cygnus.com>
- Date: Thu, 19 Aug 1999 10:12:31 +1000
- CC: binutils@sourceware.cygnus.com, gdb@sourceware.cygnus.com
- Organization: Cygnus Solutions
- References: <37BA7767.55040774@cygnus.com> <19990818165833.7196.qmail@daffy.airs.com>
Ian Lance Taylor wrote:
> So it really depends upon what you mean by the default architecture.
> For example, if you configure gas for mips4111-elf, then gas will by
> default generate object files which use the mips4111 architecture.
I'll look at what that does.
> PS: Why? I'd like GDB to make a better guess at a default
> architecture. bfd_default_arch_struct just isn't very interesting.
>
> If you explain further what you mean by this, perhaps we can think of
> some way to make it work for you. When does gdb want to know the
> default architecture? What is it going to do with the information?
Consider a GDB which has been built to support several different ISA's
(a mips4111, mips4300, ...). What architecture should GDB select by
default when it goes to talk to a remote target?
Andrew