search for: visitinlineasm

Hello, While I was trying to cross-compile Linux OMAP kernel with llvm, I have the following error message. CC arch/arm/kernel/traps.o cc1: /home/wonjeon/llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuild.cpp:5388: void llvm::SelectionDAGLowering::visitInlineAsm(llvm::CallSite): Assertion `(OpInfo.ConstraintType == TargetLowering::C_RegisterClass || OpInfo.ConstraintType == TargetLowering::C_Register) && "Unknown constraint type!"' failed. arch/arm/kernel/traps.c:748: internal compiler error: Aborted Please submit a full bug rep...

...osing multiple alternative constraints largely on the LLVM side. The Clang change is to output the multiple constraints using a '|' character in the constraint strings to delimit the alternatives. The LLVM change is as follows. In an earlier attempt, I just hacked up SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I discovered that InlineAsm::ParseConstraints was called in a couple of other places, and in one of those places (IsOperandAMemoryOperand in AddrModeMatcher.cpp), there wasn't a DAG pointe...

...put the multiple constraints using a '|' > character in the constraint strings to delimit the alternatives. This part is simple, and it can't be worse than it is now. > The LLVM change is as follows. > > In an earlier attempt, I just hacked up > SelectionDAGBuilder::visitInlineAsm, and pretty much used the same > logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. > But then I discovered that InlineAsm::ParseConstraints was called in > a couple of other places, and in one of those places > (IsOperandAMemoryOperand in AddrModeMatcher.cpp), t...

...9;|' >> character in the constraint strings to delimit the alternatives. >> > > This part is simple, and it can't be worse than it is now. > > > The LLVM change is as follows. >> >> In an earlier attempt, I just hacked up >> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >> discovered that InlineAsm::ParseConstraints was called in a couple of other >> places, and in one of those places (IsOperandAMemoryOperand in >> AddrModeMatcher...

...onstraints using a '|' > character in the constraint strings to delimit the alternatives. > > This part is simple, and it can't be worse than it is now. > > > The LLVM change is as follows. > > In an earlier attempt, I just hacked up > SelectionDAGBuilder::visitInlineAsm, and pretty much used the same > logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. > But then I discovered that InlineAsm::ParseConstraints was called in > a couple of other places, and in one of those places > (IsOperandAMemoryOperand in AddrModeMatcher.cpp), t...

...constraint strings to delimit the alternatives. >>> >> >> This part is simple, and it can't be worse than it is now. >> >> >> The LLVM change is as follows. >>> >>> In an earlier attempt, I just hacked up >>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >>> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >>> discovered that InlineAsm::ParseConstraints was called in a couple of other >>> places, and in one of those places (IsOperandAMemoryOperand in >>>...

...gt; Hello, > > While I was trying to cross-compile Linux OMAP kernel with llvm, I have the > following error message. > > CC arch/arm/kernel/traps.o > cc1: > /home/wonjeon/llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuild.cpp:5388: void > llvm::SelectionDAGLowering::visitInlineAsm(llvm::CallSite): Assertion > `(OpInfo.ConstraintType == TargetLowering::C_RegisterClass || > OpInfo.ConstraintType == TargetLowering::C_Register) && "Unknown constraint > type!"' failed. > arch/arm/kernel/traps.c:748: internal compiler error: Aborted > Pleas...

...Hello, > > While I was trying to cross-compile Linux OMAP kernel with llvm, I > have the following error message. > > CC arch/arm/kernel/traps.o > cc1: /home/wonjeon/llvm/lib/CodeGen/SelectionDAG/ > SelectionDAGBuild.cpp:5388: void > llvm::SelectionDAGLowering::visitInlineAsm(llvm::CallSite): > Assertion `(OpInfo.ConstraintType == TargetLowering::C_RegisterClass > || OpInfo.ConstraintType == TargetLowering::C_Register) && "Unknown > constraint type!"' failed. > arch/arm/kernel/traps.c:748: internal compiler error: Aborted >...

...ternatives. >>>> >>> >>> This part is simple, and it can't be worse than it is now. >>> >>> >>> The LLVM change is as follows. >>>> >>>> In an earlier attempt, I just hacked up >>>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >>>> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >>>> discovered that InlineAsm::ParseConstraints was called in a couple of other >>>> places, and in one of those places (IsOperandAMemoryOperand in...

...;> character in the constraint strings to delimit the alternatives. >> >> This part is simple, and it can't be worse than it is now. >> >> >> The LLVM change is as follows. >> >> In an earlier attempt, I just hacked up >> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same >> logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. >> But then I discovered that InlineAsm::ParseConstraints was called >> in a couple of other places, and in one of those places >> (IsOperandAMemoryOperand in AddrMod...

...;>>> >>>> This part is simple, and it can't be worse than it is now. >>>> >>>> >>>> The LLVM change is as follows. >>>>> >>>>> In an earlier attempt, I just hacked up >>>>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same logic in >>>>> TargetLowering::ComputeConstraintToUse/ChooseConstraint. But then I >>>>> discovered that InlineAsm::ParseConstraints was called in a couple of other >>>>> places, and in one of those places (IsOperandAMemor...

...ia64/crtfastmath.c) In llvm::TargetLowering::getRegForInlineAsmConstraint(), the "r" constraint (i.e. TargetLowering::C_RegisterClass) isn't handled and the function returns <pair>(0, NULL). However, it is explicitly called for that constraint by llvm::SelectionDAGLowering::visitInlineAsm(): if (OpInfo.ConstraintType == TargetLowering::C_RegisterClass) GetRegistersForValue(OpInfo, SawEarlyClobber, OutputRegs, InputRegs); Assuming the correct fix is to enhance llvm::TargetLowering::getRegForInlineAsmConstraint(), can someone give me some pointers as to how to fix it? I...

...t strings to delimit the alternatives. >>> >>> This part is simple, and it can't be worse than it is now. >>> >>> >>> The LLVM change is as follows. >>> >>> In an earlier attempt, I just hacked up >>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the same >>> logic in TargetLowering::ComputeConstraintToUse/ChooseConstraint. >>> But then I discovered that InlineAsm::ParseConstraints was called >>> in a couple of other places, and in one of those places >>> (IsOperandAMemoryOp...

...tives. >>>> >>>> This part is simple, and it can't be worse than it is now. >>>> >>>> >>>> The LLVM change is as follows. >>>> >>>> In an earlier attempt, I just hacked up >>>> SelectionDAGBuilder::visitInlineAsm, and pretty much used the >>>> same logic in TargetLowering::ComputeConstraintToUse/ >>>> ChooseConstraint. But then I discovered that >>>> InlineAsm::ParseConstraints was called in a couple of other >>>> places, and in one of those places (Is...

...was trying to cross-compile Linux OMAP kernel with llvm, I >> have the following error message. >> >> CC arch/arm/kernel/traps.o >> cc1: /home/wonjeon/llvm/lib/CodeGen/SelectionDAG/ >> SelectionDAGBuild.cpp:5388: void >> llvm::SelectionDAGLowering::visitInlineAsm(llvm::CallSite): >> Assertion `(OpInfo.ConstraintType == >> TargetLowering::C_RegisterClass || OpInfo.ConstraintType == >> TargetLowering::C_Register) && "Unknown constraint type!"' failed. >> arch/arm/kernel/traps.c:748: internal compiler error...

Dale, I've looked a bit at ChooseConstraintTuple in llvm-gcc, as well as the code generator in Clang and the inline asm handling in LLVM (ala visitInlineAsm). While I see how Clang could do it to some extent by looking at the expression types of the operands, it seems that LLVM would be in a better position for choosing multiple alternative constraints as it would know what all the operands are, and where they currently are, particularly if part of an...

...::TargetLowering::getRegForInlineAsmConstraint(), the "r" > constraint > (i.e. TargetLowering::C_RegisterClass) isn't handled and the function > returns > <pair>(0, NULL). However, it is explicitly called for that > constraint by > llvm::SelectionDAGLowering::visitInlineAsm(): It's llvm::TargetLowering::getRegClassForInlineAsmConstraint() that returns an empty vector and thus is the root case of the assert. It seems that llvm::TargetLowering::getRegForInlineAsmConstraint() is supposed to work on a single (physical) register. In GetRegistersForValue() is the fol...

...ile I was trying to cross-compile Linux OMAP kernel with llvm, I have >> the following error message. >> >> CC arch/arm/kernel/traps.o >> cc1: >> /home/wonjeon/llvm/lib/CodeGen/SelectionDAG/SelectionDAGBuild.cpp:5388: void >> llvm::SelectionDAGLowering::visitInlineAsm(llvm::CallSite): Assertion >> `(OpInfo.ConstraintType == TargetLowering::C_RegisterClass || >> OpInfo.ConstraintType == TargetLowering::C_Register) && "Unknown constraint >> type!"' failed. >> arch/arm/kernel/traps.c:748: internal compiler error: Abor...

...pes -Wmissing-prototypes -Wold-style-definition -isystem ./include -fPIC -DUSE_GAS_SYMVER -g -DHAVE_GTHR_DEFAULT -DIN_LIBGCC2 -D__GCC_FLOAT_NOT_NEEDED -c -o crtfastmath.o \ ../../llvm-gcc4.2-2.1.source/gcc/config/ia64/crtfastmath.c cc1: SelectionDAGISel.cpp:3695: void llvm::SelectionDAGLowering::visitInlineAsm(llvm::CallInst&): Assertion `!OpInfo.AssignedRegs.Regs.empty() && "Couldn't allocate input reg!"' failed. ../../llvm-gcc4.2-2.1.source/gcc/config/ia64/crtfastmath.c:37: internal compiler error: Aborted Please submit a full bug report, with preprocessed source if app...

On Jan 10, 2008, at 10:29 AM, Thomas Jablin wrote: > Hi, > > I've figured out a little more. #if defined DBX_DEBUGGING_INFO || > XCOFF_DEBUGGING_INFO guards the declaration of type_queue, however, > neither is defined on Intanium. In gt-dbxout.h type_queue's uses are > unguarded and thus are undefined on Itanium. When I compared llvm- > gcc's > gt-dbxout.h