public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "D.Venkatasubramanian, Noida" <dvenkat@noida.hcltech.com>
To: Kazu Hirata <kazu@cs.umass.edu>, Andrew.Volkov@transas.com
Cc: gcc@gcc.gnu.org, crossgcc@sources.redhat.com, gnuh8@gnuh8.org.uk,
	binutils@sources.redhat.com
Subject: RE: New targets to Binutils for H8 series
Date: Wed, 22 Jan 2003 13:43:00 -0000	[thread overview]
Message-ID: <E04CF3F88ACBD5119EFE00508BBB2121072F7723@exch-01.noida.hcltech.com> (raw)


Hi All,

I was interested in implementing some extensions to 
the H8300 simulator and was thinking of adding some 
code to crt0.S. I would like this code to be 
available when the code would be run under a 
simulator. I think it would be a good idea to add a 
target, say -msim, so that the code is generated for 
simulated target only.

In the context, I was actually trying to include 
commandline support to the simulator and so would 
have to setup the stack with the commandline 
arguments in crt0.S. I didn't think it would be a 
good idea to add the code to the default 
implementation, by adding the target, we could 
write any simulator specific code inside a 
#ifdef __SIMULATOR__ kind of structure, similar to 
the ARM implementation.

Any comments or suggestions would be useful.

Thanks and Best Regards,

Venky

             reply	other threads:[~2003-01-22  6:05 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-22 13:43 D.Venkatasubramanian, Noida [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-06  5:44 D.Venkatasubramanian, Noida
2003-01-10 17:22 Andrew Volkov
2003-01-20 13:51 ` Kazu Hirata
2003-01-10  7:45 D.Venkatasubramanian, Noida
2003-01-09 19:39 Andrew Volkov
2003-01-09 23:54 ` Kazu Hirata
2003-01-06  7:45 Shrinivas Atre
2003-01-09 14:30 ` 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=E04CF3F88ACBD5119EFE00508BBB2121072F7723@exch-01.noida.hcltech.com \
    --to=dvenkat@noida.hcltech.com \
    --cc=Andrew.Volkov@transas.com \
    --cc=binutils@sources.redhat.com \
    --cc=crossgcc@sources.redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=gnuh8@gnuh8.org.uk \
    --cc=kazu@cs.umass.edu \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).