This is the mail archive of the crossgcc@sources.redhat.com mailing list for the crossgcc project.

See the CrossGCC FAQ for lots more information.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: New targets to Binutils for H8 series

From: Kazu Hirata <kazu at cs dot umass dot edu>
To: Andrew dot Volkov at transas dot com
Cc: gcc at gcc dot gnu dot org, crossgcc at sources dot redhat dot com, gnuh8 at gnuh8 dot org dot uk, binutils at sources dot redhat dot com
Date: Sun, 19 Jan 2003 19:31:15 -0500 (EST)
Subject: Re: New targets to Binutils for H8 series
References: <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

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com

References:
- RE: New targets to Binutils for H8 series
  - From: Andrew Volkov

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]