public inbox for cgen@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Paulo Matos <pmatos@linki.tools>
Cc: cgen@sourceware.org
Subject: Re: Macro with same operands is misbehaving
Date: Mon, 08 Apr 2019 01:28:00 -0000	[thread overview]
Message-ID: <20190408012812.GD1874@redhat.com> (raw)
In-Reply-To: <2978b83b-e5eb-434d-f39b-b763782c11cf@linki.tools>

Hi -

> If I define the instruction fsgnj.s and followed by fmv.s macro, during
> disassembly `fsgnj.s` is always chosen, although assembly works fine.
> [...]
> I can't find a way to say: `fmv.s` matches for disassembly but only if
> `f1` == `f2` in `fsgnj.s f0, f1, f2`.

I don't know of a way either, at the cgen .cpu level.  But I must ask
... why is this particular disassembly heuristic seem important, given
that those are equivalent?  Anyway, it may be possible to handle at
the disassmembler driver level (in C code) even if .cpu/cgen can't
express it.

- FChE

  reply	other threads:[~2019-04-08  1:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-05 14:44 Paulo Matos
2019-04-08  1:28 ` Frank Ch. Eigler [this message]
2019-04-08  6:09   ` Paulo Matos

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=20190408012812.GD1874@redhat.com \
    --to=fche@redhat.com \
    --cc=cgen@sourceware.org \
    --cc=pmatos@linki.tools \
    /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).