From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: [PATCH: doco] gdbint.texinfo
Date: Sun, 24 Jun 2007 19:13:00 -0000 [thread overview]
Message-ID: <20070624191309.GA12571@caradoc.them.org> (raw)
In-Reply-To: <18046.4095.409804.261082@kahikatea.snap.net.nz>
On Sun, Jun 24, 2007 at 06:32:31PM +1200, Nick Roberts wrote:
> Also
>
> `gdb/ARCH-tdep.c'
> `gdb/ARCH-tdep.h'
> This often exists to describe the basic layout of the target
> machine's processor chip (registers, stack, etc.). If used, it is
> included by `TTT-tdep.h'. It can be shared among many targets
> that use the same processor.
>
> `gdb/config/ARCH/tm-ARCH.h'
> This often exists to describe the basic layout of the target
> machine's processor chip (registers, stack, etc.). If used, it is
> included by `tm-TTT.h'. It can be shared among many targets that
> use the same processor.
>
> have the same description. I presume the first is wrong.
Yes, the description for the first is somewhat wrong. The description
for the second is a bit stale - nowadays it exists for local hacks,
and we're phasing it out pretty fast. After Ulrich finished his
cleanups, there are only nine left!
--
Daniel Jacobowitz
CodeSourcery
WARNING: multiple messages have this Message-ID
From: Daniel Jacobowitz <drow@false.org>
To: gdb-patches@sourceware.org, gdb-patches@sources.redhat.com
Subject: Re: [PATCH: doco] gdbint.texinfo
Date: Sun, 24 Jun 2007 21:42:00 -0000 [thread overview]
Message-ID: <20070624191309.GA12571@caradoc.them.org> (raw)
Message-ID: <20070624214200.414I8o9HLY08DxRngmtyHp0Yylrpw5p3ECM22n544RE@z> (raw)
In-Reply-To: <18046.4095.409804.261082@kahikatea.snap.net.nz>
On Sun, Jun 24, 2007 at 06:32:31PM +1200, Nick Roberts wrote:
> Also
>
> `gdb/ARCH-tdep.c'
> `gdb/ARCH-tdep.h'
> This often exists to describe the basic layout of the target
> machine's processor chip (registers, stack, etc.). If used, it is
> included by `TTT-tdep.h'. It can be shared among many targets
> that use the same processor.
>
> `gdb/config/ARCH/tm-ARCH.h'
> This often exists to describe the basic layout of the target
> machine's processor chip (registers, stack, etc.). If used, it is
> included by `tm-TTT.h'. It can be shared among many targets that
> use the same processor.
>
> have the same description. I presume the first is wrong.
Yes, the description for the first is somewhat wrong. The description
for the second is a bit stale - nowadays it exists for local hacks,
and we're phasing it out pretty fast. After Ulrich finished his
cleanups, there are only nine left!
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2007-06-24 19:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-24 6:32 Nick Roberts
2007-06-24 18:40 ` Eli Zaretskii
2007-06-25 0:36 ` Nick Roberts
2007-06-25 10:32 ` Eli Zaretskii
2007-06-24 19:13 ` Daniel Jacobowitz [this message]
2007-06-24 21:42 ` Daniel Jacobowitz
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=20070624191309.GA12571@caradoc.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=gdb-patches@sourceware.org \
/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