public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: michal@logix.cz
Cc: binutils@sourceware.org
Subject: Re: [RFC/RFA] Proper mnemonics for VIA PadLock (i386) instructions
Date: Tue, 12 Apr 2005 20:43:00 -0000	[thread overview]
Message-ID: <200504122043.j3CKhAwO031139@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <425C305A.6000504@logix.cz> (message from Michal Ludvig on Wed, 13 Apr 2005 08:32:26 +1200)

   Date: Wed, 13 Apr 2005 08:32:26 +1200
   From: Michal Ludvig <michal@logix.cz>

   Mark Kettenis wrote:
   > This one is a bit nasty.  The OpenBSD in-tree gas has had support for
   > the VIA PadLock instructions for a while.  Unfortunately that support
   > was never submitted for inclusion into the FSF tree.  A little over a
   > year ago Michal Ludvig committed support for these instructions.
   > Unfortunately he used mnemonics that differ from the instruction names
   > as used in the VIA documentation; the VIA names include a hyphen that
   > Michal left out.  I presume Michal did this because gas doesn't accept
   > hyphens in mnemonics.  That can be fixed though.  This patch does
   > that, and adds back the missing hyphen.  It also adds a missing
   > instruction that's going to be in the VIA cpu.
   > 
   > This patch keeps hyphen-less aliases for the instructions.  The gas
   > testsuite still passes with this patch applied.

   As long as the names without hyphen still exist I don't object.
   Coincidently in Linux Journal of May 05 there is an article about VIA
   PadLock that uses the current short names (obviously).

Code using the names without the hyphen will still assemble fine.

   However, what is the point of having two names for one instruction? Why
   not to support only the one without hyphen?

Because there is already code out there that uses the hyphen.  The
reason for preferring the hyphenated names over the unhyphenated names
is that the former are used by the VIA documentation.

Cheers,

Mark

  reply	other threads:[~2005-04-12 20:43 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-12 19:15 Mark Kettenis
2005-04-12 20:32 ` Michal Ludvig
2005-04-12 20:43   ` Mark Kettenis [this message]
2005-04-13  0:38     ` Alan Modra
2005-04-13 10:43       ` Thorsten Glaser
2005-04-13 18:55       ` Mark Kettenis
2005-04-13 19:29         ` H. J. Lu
2005-04-13 19:51           ` Mark Kettenis
2005-04-13 12:29 Jan Beulich
     [not found] <s25d1e96.084@emea1-mh.id2.novell.com>
2005-04-13 15:20 ` Thorsten Glaser
2005-04-14  1:26   ` Alan Modra
2005-04-16 11:40     ` Mark Kettenis
2005-04-18  4:44       ` Alan Modra
2005-04-18 21:01         ` Mark Kettenis
2005-04-13 23:35 Marc Espie

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=200504122043.j3CKhAwO031139@elgar.sibelius.xs4all.nl \
    --to=mark.kettenis@xs4all.nl \
    --cc=binutils@sourceware.org \
    --cc=michal@logix.cz \
    /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).