public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: aram bharathi <arambharathi@linuxmail.org>
Cc: sid@sources.redhat.com
Subject: Re: how to add new instructions in gcc and test
Date: Wed, 15 Dec 2004 18:47:00 -0000	[thread overview]
Message-ID: <20041215184714.GA3659@redhat.com> (raw)
In-Reply-To: <20041214142026.4CD3621B32F@ws5-6.us4.outblaze.com>

[-- Attachment #1: Type: text/plain, Size: 924 bytes --]

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

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

      reply	other threads:[~2004-12-15 18:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-14 14:20 aram bharathi
2004-12-15 18:47 ` Frank Ch. Eigler [this message]

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=20041215184714.GA3659@redhat.com \
    --to=fche@redhat.com \
    --cc=arambharathi@linuxmail.org \
    --cc=sid@sources.redhat.com \
    /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).