From: Andrew Cagney <ac131313@redhat.com>
To: Christian Groessler <chris@groessler.org>
Cc: gdb@sources.redhat.com
Subject: Re: target z8k-coff
Date: Fri, 21 Feb 2003 15:59:00 -0000 [thread overview]
Message-ID: <3E564DEC.9060108@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0302202247340.7532-100000@ds9.reckziegel.com>
>> - meet GDB's coding standards
>
>
> Ok, I think I got this.
Yes, two things:
- run the file through gdb_indent.sh.
- run the file through gdb_ari.sh -Wcode -Wdeprecate -Wdeprecated -Winfo
(http://sources.redhat.com/gdb/current/ari)
>> - pure multi-arch
>
>
> I found http://sources.redhat.com/gdb/papers/multi-arch/ and
> http://sources.redhat.com/gdb/current/onlinedocs/gdbint_9.html#SEC79
> describing multi-arch. Is there something else I should read?
There isn't much else.
Since this is now considered a `new port', you should treat that process
as a guideline rather than a requrement. Just submit the `new port'
when ready.
BTW, GDB is very lax when it comes to adding a new port to a branch.
Also the sim directory doesn't build.
>> - contain no deprecated code
>
>
> You're referring to the current z8k-tdep.c? I will remove the deprecated
> code there.
Yes.
>> (I'm sure there is something else but I can't remember it)
>
>
> I probably will notice when it's time... :-)
Actually, I don't think there is.
As a reference (for things like frames), look at the d10v.
Andrew
next prev parent reply other threads:[~2003-02-21 15:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-18 12:54 Christian Groessler
2003-02-18 20:16 ` Andrew Cagney
2003-02-20 21:55 ` Christian Groessler
2003-02-21 15:59 ` Andrew Cagney [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-02 14:13 Christian Groessler
2001-05-08 11:50 ` Ben Elliston
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=3E564DEC.9060108@redhat.com \
--to=ac131313@redhat.com \
--cc=chris@groessler.org \
--cc=gdb@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