bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug gas/22094] New: Instruction `lsrsne` unknown


From: pmenzel+sourceware.org-bugzilla at molgen dot mpg.de
Subject: [Bug gas/22094] New: Instruction `lsrsne` unknown
Date: Wed, 06 Sep 2017 12:30:40 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=22094

            Bug ID: 22094
           Summary: Instruction `lsrsne` unknown
           Product: binutils
           Version: 2.29
            Status: UNCONFIRMED
          Severity: normal
          Priority: P2
         Component: gas
          Assignee: unassigned at sourceware dot org
          Reporter: pmenzel+sourceware.org-bugzilla at molgen dot mpg.de
  Target Milestone: ---

Using Debian Sid/unstable binutils-arm-linux-gnueabi 2.29-8.

>From the discussion of a change-set for coreboot [1], it turns out that GCC
does not understand valid instructions.

```
$ arm-linux-gnueabi-gcc-7 --version
arm-linux-gnueabi-gcc-7 (Debian 7.2.0-1) 7.2.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

$ cat mov1.S
        lsrsne r0, r0, #4
$ arm-linux-gnueabi-gcc-7 mov1.S -c -o mov1.gas
mov1.S: Assembler messages:
mov1.S:1: Error: bad instruction `lsrsne r0,r0,#4'
$ cat mov1.S
        lsrsne r0, r0, #4
$ arm-linux-gnueabi-gcc-7 mov2.S -c -o mov2.gas
```

Julius Werner comments as below.

> FWIW, the ARMv7 A.R.M. says the S comes before the condition code, so this
> should've been MOVSNE instead of MOVNES anyway. It also doesn't explicitly
> allow a source operand shift for MOV, so LSRSNE should be the correct form. I
> bet GCC just has a few additional non-standard aliases, but I would be
> surprised if it can't recognize the official and most obvious notation
> (LSRSNE).

But there is an error with gas.

[1] https://review.coreboot.org/21358/

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]