Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "D.Venkatasubramanian, Noida" <dvenkat@noida.hcltech.com>
To: "J. Johnston" <jjohnstn@redhat.com>,
	Kazu Hirata <kazu@cs.umass.edu>,
	gdb-patches@sources.redhat.com, newlib@sources.redhat.com
Cc: "D.Venkatasubramanian, Noida" <dvenkat@noida.hcltech.com>
Subject: RE: PATCH : H8300 Simulator File I/O Implementation
Date: Tue, 14 Jan 2003 04:56:00 -0000	[thread overview]
Message-ID: <E04CF3F88ACBD5119EFE00508BBB2121070C71FE@exch-01.noida.hcltech.com> (raw)

Hi All,

Just as a reminder, are the changes done to the H8300 
simulator OK, is there something else that needs to be 
done. There hasn't been any activity after the final set 
of changes.

If OK, could someone apply the patches to newlib and the 
simulator.

Regards,

Venky



> -----Original Message-----
> From: D.Venkatasubramanian, Noida 
> Sent: Wednesday, January 08, 2003 10:33 AM
> To: Kazu Hirata; gdb-patches@sources.redhat.com;
> newlib@sources.redhat.com
> Subject: RE: PATCH : H8300 Simulator File I/O Implementation
> 
> 
> Hi Kazu, 
> > 
> > Hi Venky,
> > 
> > > ;int open(const char *pathname, int flags);
> > > ;Integer arguments have to be zero extended.
> > > ;The second argument is taken from the stack,
> > > ;hence it is not zero extended here.
> > 
> > By the second argument, do you mean flags?  If so, it is in 
> regster r1
> > or er1 in all variants of H8, I think.
> 
> I meant the flags, but as this function uses variable 
> arguments, I found the
> 
> flags on the starting position on the stack and R2. As the calling
> convention 
> for variable arguments seems to be different, I get the 
> parameter from the 
> stack. If there is some improvement that can be done, I would 
> be willing to 
> do the same heartily. :-)
> 
> > 
> > Kazu Hirata
> > 
> 
> Thanks and Regards,
> 
> Venky
> 


             reply	other threads:[~2003-01-14  4:56 UTC|newest]

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

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=E04CF3F88ACBD5119EFE00508BBB2121070C71FE@exch-01.noida.hcltech.com \
    --to=dvenkat@noida.hcltech.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=jjohnstn@redhat.com \
    --cc=kazu@cs.umass.edu \
    --cc=newlib@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