Displaying 6 results from an estimated 6 matches for "isvaluevalidfortyp".
Did you mean:
isvaluevalidfortype
2004 Jul 14
1
[LLVMdev] Constants.cpp:368: error: `INT8_MAX' undeclared (first use this function)
Hi
By manipulating a #define for G++ I've managed to compile int64_t type with
ostream.
Now, I'm stopped by some to me unknown constants:
-----------------------------------
Compiling Constants.cpp
Constants.cpp: In static member function `static bool
llvm::ConstantSInt::isValueValidForType(const llvm::Type*, long long
int)':
Constants.cpp:368: error: `INT8_MAX' undeclared (first use this function)
Constants.cpp:368: error: (Each undeclared identifier is reported only once
for
each function it appears in.)
Constants.cpp:368: error: `INT8_MIN' undeclared (first use th...
2013 Jun 18
2
[LLVMdev] Failure handling half type
Here there is the dump:
SelectionDAG.cpp:81: static bool
llvm::ConstantFPSDNode::isValueValidForType(llvm::EVT, const llvm::APFloat
&): Assertion `VT.isFloatingPoint() && "Can only convert between FP types"'
failed.
0 libLLVMSupport.so 0x00007f7405022de5
llvm::sys::PrintStackTrace(_IO_FILE*) + 37
1 libLLVMSupport.so 0x00007f74050232e3
2 libpthread.so.0...
2013 Jun 29
0
[LLVMdev] Failure handling half type
Just ran into this as well. Did you ever open a a bug report about it?
On Tue, Jun 18, 2013 at 3:43 AM, Alessio Giovanni Baroni <
alessiogiovanni.baroni at gmail.com> wrote:
> Here there is the dump:
>
> SelectionDAG.cpp:81: static bool
> llvm::ConstantFPSDNode::isValueValidForType(llvm::EVT, const llvm::APFloat
> &): Assertion `VT.isFloatingPoint() && "Can only convert between FP types"'
> failed.
> 0 libLLVMSupport.so 0x00007f7405022de5
> llvm::sys::PrintStackTrace(_IO_FILE*) + 37
> 1 libLLVMSupport.so 0x00007f74050232e3...
2013 Jun 29
0
[LLVMdev] Failure handling half type
...well. Did you ever open a a bug report about it?
>
>
> On Tue, Jun 18, 2013 at 3:43 AM, Alessio Giovanni Baroni <
> alessiogiovanni.baroni at gmail.com> wrote:
>
>> Here there is the dump:
>>
>> SelectionDAG.cpp:81: static bool
>> llvm::ConstantFPSDNode::isValueValidForType(llvm::EVT, const llvm::APFloat
>> &): Assertion `VT.isFloatingPoint() && "Can only convert between FP types"'
>> failed.
>> 0 libLLVMSupport.so 0x00007f7405022de5
>> llvm::sys::PrintStackTrace(_IO_FILE*) + 37
>> 1 libLLVMSupport.so...
2013 Jun 17
0
[LLVMdev] Failure handling half type
Make sure you’re running LLVM with assertions enabled. You’ll get more information about what’s going wrong that way.
That said, yes, this looks like a bug. Specifically, SelectionDAGLegalize::ExpandConstantFP() assumes that f32 is the smallest floating point constant type it’ll need to handle, and that MVT enum ordering reflects that.
while (SVT != MVT::f32) {
2013 Jun 17
2
[LLVMdev] Failure handling half type
Hi,
if I write the following simple program:
target datalayout =
"e-p:64:64:64-i1:8:8-i8:8:8-i16:16:16-i32:32:32-i64:64:64-f32:32:32-f64:64:64-v64:64:64-v128:128:128-a0:0:64-s0:64:64-f80:128:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define void @foo () {
%1 = alloca half
store half 0xH42CC, half* %1 ; 0xH42CC = 3.4
%2 = load half* %1