public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Ian Lance Taylor <iant@google.com>
To: "Petar Bajic" <petar.bajic@micronasnit.com>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: adding movz to machine description
Date: Tue, 25 Jul 2006 13:39:00 -0000	[thread overview]
Message-ID: <m3odvdiz2i.fsf@localhost.localdomain> (raw)
In-Reply-To: <00d601c6afd2$a6f38d10$4900a8c0@niit.micronasnit.com>

"Petar Bajic" <petar.bajic@micronasnit.com> writes:

> > It may be correct for the pattern to not be matched with expand.  It's
> > OK if the if-conversion pass picks it up, which seems to be what is
> > happening for you.
> >
> > If the generated code you are getting is wrong, then problem is likely
> > in the define_insn patterns somewhere.  They don't correct represent
> > what the instruction does, or they don't correctly implement it.
> >
> > Ian
> 
> After some modifications, I managed to make gcc use my define_expand -
> I see it in debug.11.ce1 and following files, but then it disapears in
> debug.17.combine, and in the end it does not appear in asm code. How
> to find out what kills it? :)

That means that the combine pass has replaced it with something else
which is equivalent which the combine pass thought would be cheaper.
Look at the generated RTL to see what it turned into.  If the
resulting code is less efficient to run, then you need to adjust your
costs (the TARGET_RTX_COSTS hook).

Ian

  reply	other threads:[~2006-07-25 13:39 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-21  9:55 Petar Bajic
2006-07-21 16:30 ` Ian Lance Taylor
2006-07-25 10:09   ` Petar Bajic
2006-07-25 13:39     ` Ian Lance Taylor [this message]
2006-07-25 14:10       ` Petar Bajic
2006-07-25 14:56         ` Ian Lance Taylor
2006-08-11 12:07       ` Petar Bajic
  -- strict thread matches above, loose matches on Subject: below --
2006-07-07 13:54 Help required for c to VCG GDL flow chart Sharad Pratap
2006-07-07 14:24 ` adding movz to machine description Petar Bajic
2006-07-07 17:39   ` Ian Lance Taylor
2006-07-12 11:10     ` Petar Bajic
2006-07-13  7:52       ` Ian Lance Taylor
2006-07-18 12:06         ` Petar Bajic
2006-07-18 14:35           ` Ian Lance Taylor
2006-07-25 18:25   ` Rask Ingemann Lambertsen

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=m3odvdiz2i.fsf@localhost.localdomain \
    --to=iant@google.com \
    --cc=gcc-help@gcc.gnu.org \
    --cc=petar.bajic@micronasnit.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).