From: Marko Mlinar <markom@opencores.org>
To: Andrew Cagney <ac131313@ges.redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: Merging OC gdb with official gdb
Date: Sun, 08 Sep 2002 23:07:00 -0000 [thread overview]
Message-ID: <200209090807.04987.markom@opencores.org> (raw)
In-Reply-To: <3D77B310.50009@ges.redhat.com>
Andrew,
> The current documentation is being updated (slowly). Also see the thread:
>
> http://sources.redhat.com/ml/gdb/2002-07/msg00202.html
>
> but unless your architecture is really wierd, nothing should be needed.
no, it is very similar to PPC, it is very clean RISC implementation.
> - getting it to strictly use the multi-arch framework (the exception
> being if your platform has shared libraries)
I don't quite understand what you mean with "if your platform has shared
libraries", can you rephrase please.
I saw multi-arch framework would require a lot of work for our target, it
would be nice if we could make it without it.
We have following deprecated macros:
#define EXTRACT_RETURN_VALUE(TYPE, REGBUF, VALBUF)
#define STORE_RETURN_VALUE(TYPE,VALBUF)
#define EXTRACT_STRUCT_VALUE_ADDRESS(REGBUF)
Is it possible to solve them without multi-arch?
> - getting it to comply to gnu (and GDB) coding standards
of course.
> - FSF paperwork
already have it.
> Otherwize it should drop in. Take a look at one of the very recent
> targets (xstormy16?).
ok.
thanks for your help,
Marko
next prev parent reply other threads:[~2002-09-09 6:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 3:57 Marko Mlinar
2002-09-05 12:40 ` Andrew Cagney
2002-09-08 23:07 ` Marko Mlinar [this message]
2002-09-09 9:01 ` Andrew Cagney
2002-09-16 4:29 ` Marko Mlinar
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=200209090807.04987.markom@opencores.org \
--to=markom@opencores.org \
--cc=ac131313@ges.redhat.com \
--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