From: Andrew Cagney <ac131313@cygnus.com>
To: Jim Blandy <jimb@cygnus.com>
Cc: gdb@sources.redhat.com
Subject: Re: FRAME_ARGS_SKIP
Date: Mon, 25 Jun 2001 21:20:00 -0000 [thread overview]
Message-ID: <3B380D89.90203@cygnus.com> (raw)
In-Reply-To: <npofrbvq87.fsf@zwingli.cygnus.com>
> Is your target pure multi-arch? The gdbarch code does many many more
>> startup checks on such targets.
>>
>> Andrew
>
>
> The complete contents of its tm-*.h file are:
>
> /* This target uses an architecture vector exclusively. */
>
> #define GDB_MULTI_ARCH 1
>
>
> So I'm guessing that should be GDB_MULTI_ARCH should actually be set
> to GDB_MULTI_ARCH_PURE. Is that right?
In that case you don't even need a tm.h. Instead tweek the end of
configure.tgt so that it is something like the m68hc11.
Andrew
prev parent reply other threads:[~2001-06-25 21:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-14 11:07 FRAME_ARGS_SKIP Jim Blandy
2001-06-15 0:10 ` FRAME_ARGS_SKIP Andrew Cagney
[not found] ` <npu21doxx4.fsf@zwingli.cygnus.com>
2001-06-19 9:22 ` FRAME_ARGS_SKIP Andrew Cagney
2001-06-25 21:06 ` FRAME_ARGS_SKIP Jim Blandy
2001-06-25 21:20 ` Andrew Cagney [this message]
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=3B380D89.90203@cygnus.com \
--to=ac131313@cygnus.com \
--cc=gdb@sources.redhat.com \
--cc=jimb@cygnus.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