Displaying 3 results from an estimated 3 matches for "allowsmemory".
Did you mean:
allocmemory
2010 Aug 13
1
[LLVMdev] inline asm constraints in LLVM
...pplied to.
2. Clang might need some change to the constraint representation with
respeced to the logic it uses to determine if an operand is to be indirect
(using "*"), because seeing "r" and "m" in alternatives results in both the
"allowsRegister" and "allowsMemory" flags being set, and the allowsMemory
flag is used to add the indirect flag. However, I saw code in LLVM that
will insert code for the indirection even if the indirect flag is not
present, such that I think we might be able to eliminate that flag and let
LLVM deal with it.
3. LLVM needs cod...
2010 Jul 29
0
[LLVMdev] inline asm constraints in LLVM
The LLVM asm parser doesn't support multiple alternative constraints;
you need to have Clang pick one tuple in the front end. See
ChooseConstraintTuple in llvm-gcc for prior art.
On Jul 29, 2010, at 11:36 AMPDT, John Thompson wrote:
> I'm trying to fix the handling of multiple alternate constraints in
> Clang (see
2010 Jul 29
3
[LLVMdev] inline asm constraints in LLVM
I'm trying to fix the handling of multiple alternate constraints in Clang
(see
http://gcc.gnu.org/onlinedocs/gcc/Multi_002dAlternative.html#Multi_002dAlternative
).
How should the constraints be represented in the .ll file?
Clang currently will assert because the code generator sees a constraints
string with the wrong number of comma-separated items.
Basically, after some editing, it just