Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@redhat.com>
To: Kei Sakamoto <sakamoto.kei@renesas.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [patch] New m32r remote target, m32rsdi
Date: Fri, 05 Sep 2003 14:21:00 -0000	[thread overview]
Message-ID: <3F589BD7.5080506@redhat.com> (raw)
In-Reply-To: <012d01c37359$e3f98510$5169910a@KEI>

> Hello,
> 
> I posted the following two weeks ago, but there is no reaction
> so far.
> 
> Its patch adds a new remote protocol to m32r architecture and
> does not influence any other functions. So I think it's safe
> to add.

Dig dig, ah I see Daniel wrote:

> I don't feel qualified to review a new remote target, so you'll have to
> ask the remote maintainer.  However, there's definitely a problem with
> the new code.  It's full of pieces like:
> 
> 	  if (TARGET_BYTE_ORDER == BFD_ENDIAN_BIG)
> 	    *((unsigned long *) (buf + 1)) = pc_addr;
> 	  else
> 	    *((unsigned long *) (buf + 1)) = pc_addr - 1;
> 
> This sends host-endian data over the wire to the target.  Run it on a
> big-endian host and bad things will happen.

I guess that means me (but I'm only listed for remote.c :-).  I'll look
over the revision.

> I'm going to commit it next weak. Please let me know if there
> is any problem.

That wouldn't be a good idea.

Andrew



  reply	other threads:[~2003-09-05 14:21 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-04  7:57 Kei Sakamoto
2003-08-17 21:03 ` Daniel Jacobowitz
2003-08-21  4:29   ` Kei Sakamoto
2003-09-05  2:59     ` Kei Sakamoto
2003-09-05 14:21       ` Andrew Cagney [this message]
2003-09-08  6:13         ` Kei Sakamoto
2003-09-22  7:14   ` Andrew Cagney
2003-10-02  2:26     ` Kei Sakamoto
2003-10-10  1:41       ` Andrew Cagney
2003-10-14  7:53         ` Kei Sakamoto
2003-10-15  5:51           ` Eli Zaretskii
2003-10-15 14:40           ` Andrew Cagney
2003-10-16  2:43           ` Kei Sakamoto

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=3F589BD7.5080506@redhat.com \
    --to=ac131313@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=sakamoto.kei@renesas.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