| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
|
|
|
| |
llvm-svn: 162288
|
|
|
|
|
|
|
|
| |
These require special handling, which we don't currently handle. This is being
put in place to ensure we don't do invalid symbol table lookups or try to parse
invalid assembly. The test cases just makes sure the latter isn't happening.
llvm-svn: 162050
|
|
|
|
| |
llvm-svn: 162038
|
|
|
|
|
|
|
|
| |
variables, function or label references. The former is a potential clobber.
The latter is either an input or an output. Unfortunately, it's difficult to
test this patch at the moment, but the added test case will eventually do so.
llvm-svn: 162026
|
|
|
|
| |
llvm-svn: 161991
|
|
|
|
|
|
|
|
|
|
|
|
| |
statement. For example,
if (x)
__asm out dx, ax __asm out dx, ax
results in a single inline asm statement (i.e., both "out dx, ax" statements are
predicated on if(x)).
llvm-svn: 161986
|
|
|
|
|
|
|
| |
This is a reapplication of r161914 now that the scoping issue has been resolved
in r161966.
llvm-svn: 161967
|
|
|
|
| |
llvm-svn: 161931
|
|
|
|
| |
llvm-svn: 161914
|
|
|
|
| |
llvm-svn: 161908
|
|
|
|
| |
llvm-svn: 161890
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The AsmParser expects a single asm instruction, but valid ms-style inline asm
statements may contain multiple instructions.
This happens with asm blocks
__asm {
mov ebx, eax
mov ecx, ebx
}
or when multiple asm statements are adjacent to one another
__asm mov ebx, eax
__asm mov ecx, ebx
and
__asm mov ebx, eax __asm mov ecx, ebx
Currently, asm blocks are not properly handled.
llvm-svn: 161780
|
|
|
|
| |
llvm-svn: 161642
|
|
|
|
|
|
| |
only machine specific clobbers are modeled.
llvm-svn: 161524
|
|
crashers at the moment (and coincidentally this case was causing a crash).
llvm-svn: 161520
|