[llvm-bugs] [Bug 35831] New: After r315899, labels after x86 prefixes cause errors
via llvm-bugs
llvm-bugs at lists.llvm.org
Thu Jan 4 16:43:14 PST 2018
https://bugs.llvm.org/show_bug.cgi?id=35831
Bug ID: 35831
Summary: After r315899, labels after x86 prefixes cause errors
Product: new-bugs
Version: trunk
Hardware: PC
OS: All
Status: NEW
Severity: release blocker
Priority: P
Component: new bugs
Assignee: unassignedbugs at nondot.org
Reporter: dimitry at andric.com
CC: llvm-bugs at lists.llvm.org
Related to bug 35741, after https://reviews.llvm.org/rL315899 (fixing
x86 prefix issues related to bug 7709, bug 17697, bug 19251, bug 32809
and bug 21640), labels directives directly after an x86 instruction
prefix are no longer accepted.
For example (this is derived from openjdk8 sources, see [1]):
cmp $0, %edx
je 1f
lock
1: cmpxchgl %ecx,(%rdi)
This is accepted by both clang before r315899 and GNU as, but clang r315899
gives:
lock-label.s:4:2: error: unknown token in expression
1: cmpxchgl %ecx,(%rdi)
^
lock-label.s:2:5: error: directional label undefined
je 1f
^
[1]
http://hg.openjdk.java.net/jdk8/jdk8/hotspot/file/87ee5ee27509/src/os_cpu/linux_x86/vm/atomic_linux_x86.inline.hpp#l48
--
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-bugs/attachments/20180105/8b8094b7/attachment-0001.html>
More information about the llvm-bugs
mailing list