Displaying 8 results from an estimated 8 matches for "assignedregs".
2008 May 20
0
[LLVMdev] [ia64] Assertion failed: (!OpInfo.AssignedRegs.Regs.empty() && "Couldn't allocate input reg!")
[correction]
On May 20, 2008, at 1:45 PM, Marcel Moolenaar wrote:
> All,
>
> The following IR is causing the assert:
>
> \begin{ll}
> ; ModuleID = 'x.bc'
> target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-
> i64:32:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-
> f80:128:128"
> target triple =
2008 May 20
1
[LLVMdev] [ia64] Assertion failed: (!OpInfo.AssignedRegs.Regs.empty() && "Couldn't allocate input reg!")
On Tue, 20 May 2008, Marcel Moolenaar wrote:
> On May 20, 2008, at 1:45 PM, Marcel Moolenaar wrote:
>> The following IR is causing the assert:
The issue here is that the IA64 backend doesn't have inline asm support
yet. This should be pretty easy to add. Take a look at the X86 version:
X86TargetLowering::getRegForInlineAsmConstraint
it just maps "r" onto the GPR
2008 May 20
2
[LLVMdev] [ia64] Assertion failed: (!OpInfo.AssignedRegs.Regs.empty() && "Couldn't allocate input reg!")
All,
The following IR is causing the assert:
\begin{ll}
; ModuleID = 'x.bc'
target datalayout = "e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-
i64:32:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-
f80:128:128"
target triple = "ia64-portbld-freebsd8.0"
define void @__ia64_set_fast_math() nounwind {
entry:
tail call void asm sideeffect "mov.m
2008 Sep 06
2
[LLVMdev] Visibility warning
Unlike those happy few who are seeing thousands of visibility
warnings, I get only one with gcc 4.3:
lib/CodeGen/SelectionDAG/SelectionDAGBuild.cpp:3889: warning: ‘llvm::SDISelAsmOperandInfo’ declared with greater visibility than the type of its field ‘llvm::SDISelAsmOperandInfo::AssignedRegs’
Anyway know what this is about?
Ciao,
Duncan.
2008 Sep 08
0
[LLVMdev] Visibility warning
...se happy few who are seeing thousands of visibility
> warnings, I get only one with gcc 4.3:
>
> lib/CodeGen/SelectionDAG/SelectionDAGBuild.cpp:3889: warning:
> ‘llvm::SDISelAsmOperandInfo’ declared with greater visibility than
> the type of its field ‘llvm::SDISelAsmOperandInfo::AssignedRegs’
>
> Anyway know what this is about?
>
> Ciao,
>
> Duncan.
>
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
2008 Jan 10
0
[LLVMdev] LLVM Build Problems on Itanium
..../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 appropriate.
See <URL:http://developer.apple.com/bugrep...
2008 Jan 10
2
[LLVMdev] LLVM Build Problems on Itanium
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
2008 Jan 10
2
[LLVMdev] LLVM Build Problems on Itanium
..._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 appropriate.
> See <UR...