Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Kazu Hirata <kazu@cs.umass.edu>
To: dvenkat@noida.hcltech.com
Cc: gdb-patches@sources.redhat.com, binutils@sources.redhat.com
Subject: Re: PATCH : H8300 Simulator File I/O Implementation
Date: Sat, 30 Nov 2002 10:01:00 -0000	[thread overview]
Message-ID: <20021130.130027.74732311.kazu@cs.umass.edu> (raw)
In-Reply-To: <E04CF3F88ACBD5119EFE00508BBB212105D59B4C@exch-01.noida.hcltech.com>

Hi Venky,

You might want to send your patch to newlib@sources.redhat.com as
well, possibly after separating the patch for individual projects
(binutils, newlib, and gdb-patches)!?

! 		  /* And a jsr to these locations are turned into magic traps. */
  		  if (dst->opcode == O (O_JSR, SB))
  		    {
! 		      if (dst->src.literal == 0xc5)

This may be up to your preference, but what about "switch (dst->src.literal)"?

! 	    /* Setting filename_ptr to first argument of open */
! 	    filename_ptr = cpu.regs[0];

I think the GNU coding standard prefers a complete sentence (well,
except the subject) ending with a period and two spaces like

  /* Set filename_ptr to the first argument of open.   */

! 	    /* Allocating space for the filename */
! 	    filename = (char *)malloc(sizeof(char) * len);

Do you free this filename somewhere?

Thanks,

Kazu Hirata


  reply	other threads:[~2002-11-30 18:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-29 21:31 D.Venkatasubramanian, Noida
2002-11-30 10:01 ` Kazu Hirata [this message]
2003-03-04 16:08   ` Andrew Cagney
2003-03-04 16:33     ` Kazu Hirata
2002-12-02  3:45 D.Venkatasubramanian, Noida
2002-12-23 22:59 D.Venkatasubramanian, Noida
2002-12-24  6:51 ` Kazu Hirata
2002-12-26  4:38 D.Venkatasubramanian, Noida
2002-12-26 10:12 D.Venkatasubramanian, Noida
2002-12-31  2:00 D.Venkatasubramanian, Noida
2002-12-31  4:42 ` Kazu Hirata
2003-01-03  8:30 D.Venkatasubramanian, Noida
2003-01-07 22:00 ` Kazu Hirata
2003-01-07 23:08 ` Andrew Cagney
2003-01-08  5:08 D.Venkatasubramanian, Noida
2003-01-14  4:56 D.Venkatasubramanian, Noida

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=20021130.130027.74732311.kazu@cs.umass.edu \
    --to=kazu@cs.umass.edu \
    --cc=binutils@sources.redhat.com \
    --cc=dvenkat@noida.hcltech.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