From: Ian Lance Taylor <ian@wasabisystems.com>
To: Savithri Venkatachalapathy <snvpathy@yahoo.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Porting GCC to new target
Date: Fri, 05 Dec 2003 14:04:00 -0000 [thread overview]
Message-ID: <m3ad67tl73.fsf@gossamer.airs.com> (raw)
In-Reply-To: <20031205052930.62482.qmail@web14206.mail.yahoo.com>
Savithri Venkatachalapathy <snvpathy@yahoo.com> writes:
> While porting gcc to new target, I am not able to
> figure how to handle branch instructions.
> The .md descriptions of the bne, beq instructions take
> 3 rtx parameters while the expr.c, stmt.c, rtl.h,
> loop.c, unroll.c and optabe.c files have gen-beq(),
> gen-bne() prototypes which take only 1 rtx parameter.
> Hence when I try to 'make' it gives error saying that
> the prototypes of gen-beq() in the files mentioned
> above does not match with the prototype from the .md
> file.
>
> Could anybody tell me how to overcome this. DO I need
> to download different versions of the 6 files
> mentioned above which have branch prototypes taking 3
> parameters.
From
http://gcc.gnu.org/onlinedocs/gccint/Jump-Patterns.html#Jump%20Patterns
Some machines have compare-and-branch instructions and no
condition code. A similar technique works for them. When it is
time to "output" a compare instruction, record its operands in two
static variables. When outputting the branch-on-condition-code
instruction that follows, actually output a compare-and-branch
instruction that uses the remembered operands.
See, e.g., the MIPS target "cmpsi" and "beq" patterns.
Ian
next prev parent reply other threads:[~2003-12-05 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-05 5:29 Savithri Venkatachalapathy
2003-12-05 14:04 ` Ian Lance Taylor [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-10 8:24 Savithri Venkatachalapathy
[not found] <20031114091925.68490.qmail@web14203.mail.yahoo.com>
2003-11-14 16:06 ` Dara Hazeghi
2003-11-21 6:13 ` Savithri Venkatachalapathy
2003-11-11 7:37 Dara Hazeghi
2003-11-12 7:28 ` Savithri Venkatachalapathy
2003-11-14 7:17 ` Dara Hazeghi
2003-11-11 4:39 Savithri Venkatachalapathy
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=m3ad67tl73.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=gcc-help@gcc.gnu.org \
--cc=snvpathy@yahoo.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).