From: Kazu Hirata <kazu@cs.umass.edu>
To: 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: Mon, 20 Jan 2003 13:51:00 -0000 [thread overview]
Message-ID: <20030119.193115.59647218.kazu@cs.umass.edu> (raw)
In-Reply-To: <2E74F312D6980D459F3A05492BA40F8D01BE6F88@clue.transas.com>
Hi Andrew,
> > This way, we don't have to have separate libgcc.a and lib[mc].a, etc, for
> > H8S/2600 because the difference of instruction sets between H8S and
> > H8S/200 is only mac-related instructions.
>
> At present you are right, but:
> 1) what about using MAC in lib[mc], in future releases of newlib?
> 2) what about interrupt frames in library routines?
Actually I have to admit that the interrupt frame does not save mac
yet. I think one reasonable implementation is to save the mac
register in a function that uses it because not every function uses
it. In other words, we probably do not want to make it a
call-clobbered register.
By the way, Hitachi just released H8SX, an update to H8S series, so we
want to have something like .h8sx.
Kazu Hirata
next prev parent reply other threads:[~2003-01-20 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 17:22 Andrew Volkov
2003-01-20 13:51 ` Kazu Hirata [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-06 5:44 D.Venkatasubramanian, Noida
2003-01-22 13:43 D.Venkatasubramanian, Noida
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=20030119.193115.59647218.kazu@cs.umass.edu \
--to=kazu@cs.umass.edu \
--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 \
/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).