From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 31573 invoked by alias); 20 Jan 2003 00:31:30 -0000 Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-owner@gcc.gnu.org Received: (qmail 31536 invoked from network); 20 Jan 2003 00:31:28 -0000 Received: from unknown (HELO mail.cs.umass.edu) (128.119.243.168) by 172.16.49.205 with SMTP; 20 Jan 2003 00:31:28 -0000 Received: from localhost (IDENT:TXtH1MynZMzKvjWsg/DN/JIbvKchGlng@loki.cs.umass.edu [128.119.243.168]) by mail.cs.umass.edu (8.12.6/8.12.5) with ESMTP id h0K0VQ1c019254; Sun, 19 Jan 2003 19:31:27 -0500 Date: Mon, 20 Jan 2003 13:51:00 -0000 Message-Id: <20030119.193115.59647218.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 From: Kazu Hirata In-Reply-To: <2E74F312D6980D459F3A05492BA40F8D01BE6F88@clue.transas.com> References: <2E74F312D6980D459F3A05492BA40F8D01BE6F88@clue.transas.com> Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Checked: This message probably not SPAM X-Spam-Score: -3.4, Required: 5 X-Spam-Tests: IN_REP_TO X-Spam-Report: SPAM: -3.4 hits, 5 required; SPAM: * -3.4 -- Found a In-Reply-To header X-Scanned-By: MIMEDefang 2.26 (www . roaringpenguin . com / mimedefang) X-SW-Source: 2003-01/txt/msg00922.txt.bz2 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