From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 28366 invoked by alias); 15 Dec 2004 18:47:32 -0000 Mailing-List: contact sid-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: sid-owner@sources.redhat.com Received: (qmail 28288 invoked from network); 15 Dec 2004 18:47:26 -0000 Received: from unknown (HELO mx1.redhat.com) (66.187.233.31) by sourceware.org with SMTP; 15 Dec 2004 18:47:26 -0000 Received: from int-mx1.corp.redhat.com (int-mx1.corp.redhat.com [172.16.52.254]) by mx1.redhat.com (8.12.11/8.12.11) with ESMTP id iBFIlQBK014725 for ; Wed, 15 Dec 2004 13:47:26 -0500 Received: from pobox.toronto.redhat.com (pobox.toronto.redhat.com [172.16.14.4]) by int-mx1.corp.redhat.com (8.11.6/8.11.6) with ESMTP id iBFIlKr29825; Wed, 15 Dec 2004 13:47:20 -0500 Received: from touchme.toronto.redhat.com (IDENT:postfix@touchme.toronto.redhat.com [172.16.14.9]) by pobox.toronto.redhat.com (8.12.8/8.12.8) with ESMTP id iBFIlGoS031689; Wed, 15 Dec 2004 13:47:20 -0500 Received: from toenail.toronto.redhat.com (toenail.toronto.redhat.com [172.16.14.211]) by touchme.toronto.redhat.com (Postfix) with ESMTP id 1BEF3800001; Wed, 15 Dec 2004 13:47:16 -0500 (EST) Received: from toenail.toronto.redhat.com (localhost.localdomain [127.0.0.1]) by toenail.toronto.redhat.com (8.12.10/8.12.5) with ESMTP id iBFIlFB3027078; Wed, 15 Dec 2004 13:47:15 -0500 Received: (from fche@localhost) by toenail.toronto.redhat.com (8.12.10/8.12.10/Submit) id iBFIlFbp027076; Wed, 15 Dec 2004 13:47:15 -0500 Date: Wed, 15 Dec 2004 18:47:00 -0000 From: "Frank Ch. Eigler" To: aram bharathi Cc: sid@sources.redhat.com Subject: Re: how to add new instructions in gcc and test Message-ID: <20041215184714.GA3659@redhat.com> References: <20041214142026.4CD3621B32F@ws5-6.us4.outblaze.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="s0H35NU0PUc8VBh+" Content-Disposition: inline In-Reply-To: <20041214142026.4CD3621B32F@ws5-6.us4.outblaze.com> User-Agent: Mutt/1.4.1i X-SW-Source: 2004-q4/txt/msg00024.txt.bz2 --s0H35NU0PUc8VBh+ Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-length: 924 Hi - On Tue, Dec 14, 2004 at 08:20:25PM +0600, aram bharathi wrote: > [...] > i like to upgrade the gcc with some more extra instructions for the ARM > processor. but if i write the new instruction then how can i check the > newly added instructions are working correctly or not. and how can i > verify the output is correct!!! [...] You need some way of getting gcc to trigger those extra instructions, whether it's inline assembly or something else. Add such a program to the gcc test suite, and include assertions to confirm that the instructions did the right thing (assuming they change simple testable state like memory or registers). Then you need to update one of the arm simulators (the one in gdb, or sid's cgen version) to model the new instructions. This part of the work is not well documented, but it's not too scary. Finally, you run the gcc test suite against the arm simulator of your choice. - FChE --s0H35NU0PUc8VBh+ Content-Type: application/pgp-signature Content-Disposition: inline Content-length: 189 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.3 (GNU/Linux) iD8DBQFBwIayVZbdDOm/ZT0RAirwAJ0ZDWIm1kWHcQvO3urRdmjVj0zxPQCfT1T2 7dIntJNLJhd+VBhfFGASLxE= =95xC -----END PGP SIGNATURE----- --s0H35NU0PUc8VBh+--