From: Elena Zannoni <ezannoni@localhost.redhat.com>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Elena Zannoni <ezannoni@redhat.com>,
Andrew Cagney <ac131313@cygnus.com>,
bje@redhat.com, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] New gdb port: Hitachi SH5 (sh64-elf)
Date: Sun, 10 Feb 2002 19:45:00 -0000 [thread overview]
Message-ID: <15463.15898.564085.250660@localhost.redhat.com> (raw)
In-Reply-To: <orbsezbab8.fsf@free.redhat.lsd.ic.unicamp.br>
Alexandre Oliva writes:
> On Feb 8, 2002, Elena Zannoni <ezannoni@redhat.com> wrote:
>
> > Alexandre Oliva writes:
> >> On Feb 8, 2002, Elena Zannoni <ezannoni@localhost.redhat.com> wrote:
> >>
> >> > If we had opcodes compile also
> >> > the sh64 files whe the target is sh-elf, the problem would go away.
> >>
> >> You may assume this to be the case. I'm going to implement this
> >> change tomorrow. If I don't, please bug me.
>
> > Really? Great! Thanks so much!
>
> Ok, the change is now in.
>
> Note that sh3eb-linux, for example, still doesn't get SH64 support;
> only sh64-* and sh-* do. I don't know whether this matters for GDB.
>
Thanks, Alex. With yours and H-P fixes in bfd, I can get rid of
the GDB_TARGET_IS_SH64 thing. But I am still missing the simulator
bits before I can commit this, or it won't build.
Elena
> --
> Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
> Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
> CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
> Free Software Evangelist Professional serial bug killer
prev parent reply other threads:[~2002-02-11 3:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-07 20:32 Elena Zannoni
2002-02-07 20:59 ` Andrew Cagney
2002-02-07 21:22 ` Elena Zannoni
2002-02-07 23:53 ` Alexandre Oliva
2002-02-08 5:36 ` Elena Zannoni
2002-02-08 19:31 ` Alexandre Oliva
2002-02-10 19:45 ` Elena Zannoni [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=15463.15898.564085.250660@localhost.redhat.com \
--to=ezannoni@localhost.redhat.com \
--cc=ac131313@cygnus.com \
--cc=aoliva@redhat.com \
--cc=bje@redhat.com \
--cc=ezannoni@redhat.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