public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: Dave Brolley <brolley@redhat.com>
To: Joern Rennecke <joernr@arc.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, cgen@sources.redhat.com
Subject: Re: delayed branches and zero overhead loops
Date: Wed, 14 Feb 2007 17:09:00 -0000	[thread overview]
Message-ID: <45D34205.9000209@redhat.com> (raw)
In-Reply-To: <20070213222044.GA31512@elsdt-razorfish.arc.com>

Joern Rennecke wrote:

>On Tue, Feb 13, 2007 at 04:11:52PM -0500, Frank Ch. Eigler wrote:
>  
>
>>The decoder generator is fully automatic.  If you represent decodable
>>bits without cheating, it will do a reasonable job.
>>    
>>
>
>I which that were the case.  Try to generate the decoder for the attached
>file; it warns about one alledged Decoder ambiguity for j_L_r_r [$RC-noilink]
>versus j_L_r_r [$RC-ilink] .  The values for $RC-ilink and $RC-noilink are
>disjoint.  I've also tried to use a decode-split on this problem, but to
>no avail.
>  
>
The problem is that RC-ilink and RC-noilink are operands. They do not 
participate in insn decoding. If there are no other differences in the 
fixed fields of the insns (it's hard to tell because of the complexity 
of your pmacros), then there will be an ambiguity. If you add enough 
"-v"s to CGENFLAGS when you run your make, you will get a dump of the 
pmacro-expanded input.

Dave

  reply	other threads:[~2007-02-14 17:09 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-13 15:37 Joern Rennecke
2007-02-13 18:51 ` Frank Ch. Eigler
2007-02-13 21:00   ` Joern Rennecke
2007-02-13 21:12     ` Frank Ch. Eigler
2007-02-13 22:21       ` Joern Rennecke
2007-02-14 17:09         ` Dave Brolley [this message]
2007-02-14 18:30           ` Joern Rennecke
2007-02-14 19:52             ` Dave Brolley
2007-02-14 20:15               ` Joern Rennecke
2007-02-16 20:54                 ` Dave Brolley
2007-02-19  3:39                   ` Joern Rennecke
     [not found]                     ` <45D9C06A.4030903@redhat.com>
2007-02-19 15:56                       ` Joern Rennecke
2007-02-19 16:07                         ` Frank Ch. Eigler
2007-02-19 18:14                           ` Joern Rennecke
2007-02-19 18:19                             ` Dave Brolley
2007-02-22 15:50                               ` Joern Rennecke
2007-02-22 16:08                               ` insert evaluation for multi-ifields broken Joern Rennecke
2007-02-22 16:56                                 ` Dave Brolley
2007-02-22 18:14                                   ` Joern Rennecke
2007-02-23 17:45                                     ` Dave Brolley
2007-02-15 16:54               ` delayed branches and zero overhead loops Joern Rennecke
2007-02-14 18:58       ` decode-bitsize (Was: Re: delayed branches and zero overhead loops) Joern Rennecke
2007-02-13 19:25 ` delayed branches and zero overhead loops Doug Evans
2007-02-13 20:38   ` Joern Rennecke
2007-02-14 18:30     ` Doug Evans
2007-02-14 19:22       ` Joern Rennecke

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=45D34205.9000209@redhat.com \
    --to=brolley@redhat.com \
    --cc=cgen@sources.redhat.com \
    --cc=fche@redhat.com \
    --cc=joernr@arc.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).