[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Bug gas/20319] New: as and objdump allow "fmov sn, xm"
From: |
cov at codeaurora dot org |
Subject: |
[Bug gas/20319] New: as and objdump allow "fmov sn, xm" |
Date: |
Thu, 30 Jun 2016 12:23:10 +0000 |
https://sourceware.org/bugzilla/show_bug.cgi?id=20319
Bug ID: 20319
Summary: as and objdump allow "fmov sn, xm"
Product: binutils
Version: unspecified
Status: UNCONFIRMED
Severity: normal
Priority: P2
Component: gas
Assignee: unassigned at sourceware dot org
Reporter: cov at codeaurora dot org
Target Milestone: ---
The assembler as assembles invalid fmov mnemonics and the disassembler objdump
disassembles invalid fmov-like opcodes as if they were valid/defined. The
situation arises if the destination register is 32 bits (for example s9) and
the source register is 64 bits (for example x0).
Steps to Reproduce as Issue:
echo fmov s9, x0 > astest.s
aarch64-linux-gnu-as astest.s -o astest
Actual Results: aarch64-linux-gnu-as completes successfully
Expected Results: aarch64-linux-gnu-as fails with informative message that only
32-bit source operands are permitted for fmov when a 32-bit destination operand
is used
Steps to Reproduce objdump Issue:
echo 0900279e | xxd -r -p > objtest
aarch64-linux-gnu-objdump -D -b binary -maarch64 objtest
Actual results: opcode disassembled as fmov s9, x0
Expected Results: opcode disassembled as .inst 0x0900279e ; undefined
--
You are receiving this mail because:
You are on the CC list for the bug.
- [Bug gas/20319] New: as and objdump allow "fmov sn, xm",
cov at codeaurora dot org <=