public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Alexander Fedotov <alfedotov@gmail.com>
To: Alan Modra <amodra@gmail.com>
Cc: Andrew Jenner <andrew@codesourcery.com>, binutils@sourceware.org
Subject: Re: [PATCH] PowerPC VLE changes
Date: Wed, 29 Mar 2017 19:36:00 -0000	[thread overview]
Message-ID: <CAN8C2CoRFhFAyoBB+JLenbx_nigtyS51oLeHNvhd2ez9sPuqqw@mail.gmail.com> (raw)
In-Reply-To: <20170328233315.GE4983@bubble.grove.modra.org>

Well, I think while such aliases are not in PowerISA and may be
changed in any moment - better to move such ones to macros table.
Performance should not harm dramatically if at all.

Anyway, don't miss decorated storage instruction for e200z4 from my patch.


On Wed, Mar 29, 2017 at 2:33 AM, Alan Modra <amodra@gmail.com> wrote:
> On Mon, Mar 27, 2017 at 03:32:23PM +0100, Andrew Jenner wrote:
>> Hi Alexander,
>>
>> On 24/03/2017 15:32, Александр Федотов wrote:
>> >I have question in continuation of
>> >https://sourceware.org/ml/binutils/2016-07/msg00342.html
>> >
>> >Why do you need to have "e_cmpwi" etc in vle_opcodes table ? It seems
>> >they are just alias names because of the same opcodes and objdump
>> >never show them.
>> >Why don't to use powerpc_macros instead ?
>
> It is the other way around.  If there is something in the macro table
> that could go in the main opcode table then it should be moved there.
>
> Mnemonic lookup in the main opcode table happens first.  Macro lookup
> is later.  So putting something in the macro table unnecessarily, just
> slows does the assembler a litte.  The macro table should really only
> be used where some manipulation of arguments is needed.
>
> Hmm, looking at the macros, that means e_rotlwi and e_clrlwi probably
> ought to be moved since the macros just provide a default argument to
> the underlying machine insn rather than some arithmetic manipulation.
> Fixing this isn't at all important though, so don't see these comments
> as a request for someone to tidy the VLE support.  Note that moving
> those insns to the main table would also allow the disassembler to
> produce e_rotlwi or e_clrlwi rather than e_rlwinm, depending on
> whether you place them before e_rlwinm or after.  I recognize that
> some people (more hardware oriented) would prefer to see rlwinm rather
> than rotlwi (likely prefered by those more software oriented).  I've
> just been working on a patch that will add -Mraw to the powerpc
> disassembler to maybe satisfy both camps.
>
> --
> Alan Modra
> Australia Development Lab, IBM



-- 
Best regards,
AF

  reply	other threads:[~2017-03-29 19:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-24 15:32 Александр Федотов
2017-03-27 14:32 ` Andrew Jenner
2017-03-28 14:14   ` Александр Федотов
2017-03-28 23:33   ` Alan Modra
2017-03-29 19:36     ` Alexander Fedotov [this message]
2017-04-04  1:29       ` Alan Modra
2017-04-04 10:23         ` Alexander Fedotov
2017-04-04 10:33           ` Alexander Fedotov
2017-04-22  8:51             ` Alan Modra
  -- strict thread matches above, loose matches on Subject: below --
2017-06-23 20:52 Alexander Fedotov
2017-06-23 20:55 ` Alexander Fedotov
2017-06-23 20:56   ` Alexander Fedotov
2017-06-23 21:34     ` Alexander Fedotov
2017-06-24 13:22       ` Alan Modra
2017-06-24 13:21     ` Alan Modra
2017-06-24 13:18   ` Alan Modra
2017-06-24 13:11 ` Alan Modra
2016-07-26 16:41 Andrew Jenner
2016-07-26 23:26 ` Alan Modra
2016-08-01 16:43   ` Andrew Jenner

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=CAN8C2CoRFhFAyoBB+JLenbx_nigtyS51oLeHNvhd2ez9sPuqqw@mail.gmail.com \
    --to=alfedotov@gmail.com \
    --cc=amodra@gmail.com \
    --cc=andrew@codesourcery.com \
    --cc=binutils@sourceware.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).