This is the mail archive of the
gdb@sources.redhat.com
mailing list for the GDB project.
Re: Multi-arch and user-control of architecture flags
- From: Richard Earnshaw <rearnsha at arm dot com>
- To: Andrew Cagney <ac131313 at cygnus dot com>
- Cc: Richard dot Earnshaw at arm dot com, Eli Zaretskii <eliz at is dot elta dot co dot il>, gdb at sources dot redhat dot com
- Date: Thu, 16 May 2002 14:59:00 +0100
- Subject: Re: Multi-arch and user-control of architecture flags
- Organization: ARM Ltd.
- Reply-to: Richard dot Earnshaw at arm dot com
> > /* Add root prefix command for all "set mips"/"show mips" commands */
> > add_prefix_cmd ("mips", no_class, set_mips_command,
> > "Various MIPS specific commands.",
> > &setmipscmdlist, "set mips ", 0, &setlist);
> >
> > add_prefix_cmd ("mips", no_class, show_mips_command,
> > "Various MIPS specific commands.",
> > &showmipscmdlist, "show mips ", 0, &showlist);
> >
>
> Just a PS on this. The command set ``set mips fpu ...'' et.al. isn't
> perfect - it sets a global for all mips which is probably sufficient for
> what people want.
>
> Eventually a per thread command may be needed. So that a target
> containing an 8086 and x86-64 can have, separatly, their disassembly
> mode. Something like:
>
> thread 5 set i386 disassembler x86-64
>
> (just ignore the syntax though). However, not our problem :-)
>
Yeah! I was thinking of a similar sort of requirement if a user has two
physical CPUs in the design, then you would need to be able to configure
each instance.
However, we would need to be able to have multiple instances of the
gdbarch current for that to work...
R.