search for: subconstraintinfo

...e might be able to eliminate that flag and let LLVM deal with it. 3. LLVM needs code to select the alterinative constraint to use. To do this, the inline asm handler probably needs to be changed to store the alternatives separately to make it easier to walk them for the selection, perhaps using a SubConstraintInfo class in an array owned by ConstraintInfo. After the selection, which determines the one subconstraint index needed, the data for the selected alternatives could then be copied to the ConstraintInfo class to reduce impact on the code using it. I'm willing to have a go at doing this myself, bu...

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

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