From: Alan Lehotsky <apl@alum.mit.edu>
To: "David Livshin" <dlivshin@internet-zahav.net>
Cc: <gcc@gcc.gnu.org>
Subject: Re: gcc port to StarCore
Date: Wed, 01 May 2002 06:32:00 -0000 [thread overview]
Message-ID: <a05111705b8f592331ad8@[63.214.85.135]> (raw)
In-Reply-To: <001301c1f113$907bf540$91d808d5@dlivshin>
At 3:23 PM +0200 5/1/02, David Livshin wrote:
>Hi,
>
>I am working on the port of the gcc version 3.0.1 to the StarCore
>architecture ( DSP from Motorola/Agere ). The compiler works fine and
>produces correct StarCore code that passes all the validations ( I have ).
>However there are cases where it can do better job:
>
>1. no constant propagation:
My "guess" would be that you don't allow CONST_INT's as operands
to the "cmpsi" patterns.
Can you post the define_expand and/or define_insn for these?
>.....
.....
--
Quality Software Management
http://home.earthlink.net/~qsmgmt
apl@alum.mit.edu
(978)287-0435 Voice
(978)808-6836 Cell
Software Process Improvement / Management Consulting
Language Design / Compiler Implementation
next prev parent reply other threads:[~2002-05-01 13:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-01 5:25 David Livshin
2002-05-01 6:32 ` Alan Lehotsky [this message]
2002-05-01 22:40 ` David Livshin
2002-05-01 23:22 ` Richard Henderson
2002-05-02 5:18 ` David Livshin
2002-05-02 5:46 ` Alan Lehotsky
2002-05-03 3:14 ` David Livshin
2002-05-03 11:38 ` Richard Henderson
2002-05-02 5:22 ` Alan Lehotsky
2002-05-02 7:38 ` David Livshin
2002-05-02 8:04 ` Alan Lehotsky
2002-05-03 3:01 ` David Livshin
2002-05-03 11:28 ` Alan Lehotsky
2002-05-17 4:17 David Livshin
2002-05-17 14:41 ` Richard Henderson
2002-05-19 23:30 ` David Livshin
2002-05-20 0:19 ` Richard Henderson
2007-02-13 8:58 David Livshin
2007-02-13 15:14 ` Ian Lance Taylor
2007-02-13 17:27 ` David Livshin
2007-02-13 17:33 ` Ian Lance Taylor
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='a05111705b8f592331ad8@[63.214.85.135]' \
--to=apl@alum.mit.edu \
--cc=dlivshin@internet-zahav.net \
--cc=gcc@gcc.gnu.org \
/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).