From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Kazu Hirata <kazu@cs.umass.edu>
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: Fri, 10 Jan 2003 17:22:00 -0000 [thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8D01BE6F88@clue.transas.com> (raw)
Hi Kazu,
>
> > Good idea, but I think also will be good, mark 26xx subtarget as
> > new bfd-target too.
>
> I am basically for having a subtarget for each combination of
> instruction set and mode. However, if we have .h2600 or something,
> then we should probably have "upward compatibility" thing built into
> the linker so that we can mix H8S/2600 code with H8S or H8/300H.
I don't think it will be a big problem, cause we told about
change numeration of bfd-subtargets, so why not take such numbers,
wich will be "upward compatible" (simly set high bit, I think)?
> 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?
Regards,
Andrey
next reply other threads:[~2003-01-10 12:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 17:22 Andrew Volkov [this message]
2003-01-20 13:51 ` Kazu Hirata
-- 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=2E74F312D6980D459F3A05492BA40F8D01BE6F88@clue.transas.com \
--to=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).