From: Jiri Smid <smid@suse.cz>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: Misc; Was: [RFA]: x86_64 target files
Date: Thu, 30 Aug 2001 01:35:00 -0000 [thread overview]
Message-ID: <s8v7kvmgd2g.fsf@naga.suse.cz> (raw)
In-Reply-To: <3B738589.4050605@cygnus.com>
Hello,
Sorry for late response - I was on vacation.
Andrew Cagney <ac131313@cygnus.com> writes:
> Jiri, some quick comments on things that caught my eye. Once the *-tdep.c file
> is multi-arched (as much as possible) I'll go review the *-nat file properly.
>
> enjoy,
> Andrew
>
> > + /* This table must line up with REGISTER_NAMES in tm-x86_64.h
> > + symbols like 'RAX' come from <sys/reg.h>. */
> > + static int regmap[] = {
> > + RAX, RDX, RCX, RBX,
> > + RSI, RDI, RBP, RSP,
> > + R8, R9, R10, R11,
> > + R12, R13, R14, R15,
> > + RIP, EFLAGS
> > + };
>
>
> You are encouraged to create a file like:
>
> x86_64-tdep.h
>
> so that this sort of thing can be shared amonst the various x86_64 specific
> files. Both *-nat and *-nat-linux contained that exact table. Just be careful
> to namespace proof things a little (x86_64 prefixes and the like).
OK.
>
> --
>
> > + /* This is the variable that is set with "set disassembly-flavor", and
> > + its legitimate values. */
> > + static const char att_flavor[] = "att";
> > + static const char intel_flavor[] = "intel";
> > + static const char *valid_flavors[] = {
> > + att_flavor,
> > + intel_flavor,
> > + NULL
> > + };
> > + static const char *disassembly_flavor = att_flavor;
> >
>
>
> Have a look at the ARM which queries opcodes for a list of disassembly variants
> instead of duplicating those variants here.
>
I have looked at ARM and there is list of dissassembly flavors
(register set names) obtained from binutils. But in i386/x86_64 case there
is no way how to get list of flavors. I am not sure what do you mean...
Changes in binutils?
>
> > + static unsigned char
> > + codestream_fill (int peek_flag)
>
>
> FYI, I don't think that the code stream stuff belongs in a *-tdep.c. Hmm,
> I suspect you accidently picked it up when clonning i386-tdep.c. Could
> I recommend going through your new *-tdep.c file and cleaning out anything that
> isn't being used.
>
OK, I removed it.
--
Jiri Smid
---------------------------------------------------------------------
SuSE CR, s.r.o. e-mail: smid@suse.cz
Drahobejlova 27 tel:+420 2 83095 373
190 00 Praha 9 fax:+420 2 83095 374
Ceska republika http://www.suse.cz
next prev parent reply other threads:[~2001-08-30 1:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-02 7:20 Jiri Smid
2001-08-02 8:39 ` Eli Zaretskii
2001-08-02 9:37 ` Andreas Jaeger
2001-08-02 9:43 ` Kevin Buettner
2001-08-09 22:53 ` Andrew Cagney
2001-08-09 23:12 ` config/i386/xm-x86_64.h; Was " Andrew Cagney
2001-08-09 23:25 ` configure.host; Was: " Andrew Cagney
2001-08-09 23:41 ` configure.tgt; " Andrew Cagney
2001-08-09 23:57 ` Misc; " Andrew Cagney
2001-08-30 1:35 ` Jiri Smid [this message]
2001-08-30 7:39 ` Andrew Cagney
2001-08-30 11:03 ` Andreas Jaeger
2001-08-30 16:53 ` Andrew Cagney
2001-08-31 0:13 ` Andreas Jaeger
2001-08-31 2:00 ` i386 flavors [Was: Re: Misc; Was: [RFA]: x86_64 target files] Andreas Jaeger
2001-08-31 10:39 ` Misc; Was: [RFA]: x86_64 target files Andrew Cagney
2001-08-31 13:12 ` Andreas Jaeger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=s8v7kvmgd2g.fsf@naga.suse.cz \
--to=smid@suse.cz \
--cc=ac131313@cygnus.com \
--cc=gdb-patches@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox