Displaying 15 results from an estimated 15 matches for "isfloatti".
Did you mean:
isfloatty
2011 Nov 14
2
[LLVMdev] Transferring value* in LLVM
yes - i checked that the src->getType()->isFloatTy() is true
Yakov
On Mon, Nov 14, 2011 at 8:24 PM, Duncan Sands <baldrick at free.fr> wrote:
> On 14/11/11 19:20, Yakov Malinkovich wrote:
>
>> I sure that is.
>>
>
> Did you test it? Can you do: src->getType()->isFloatTy()
>
>
> What could be other reasons for such error?
>
> The only
2011 Nov 14
2
[LLVMdev] Transferring value* in LLVM
Here is the error that I get:
Assertion failed: (i >= FTy->getNumParams() || FTy->getParamType(i) ==
Params[i]->getType()) && "Calling a function with a bad signature!"
Yakov
On Mon, Nov 14, 2011 at 9:05 PM, Eric Christopher <echristo at apple.com>wrote:
> You'll probably need to dump both the source and the dest and show the
> code that's being
2011 Nov 14
0
[LLVMdev] Transferring value* in LLVM
You'll probably need to dump both the source and the dest and show the code that's being generated. A lot of guessing here that's not getting us very far very fast.
-eric
On Nov 14, 2011, at 10:56 AM, Yakov Malinkovich wrote:
> yes - i checked that the src->getType()->isFloatTy() is true
> Yakov
>
>
> On Mon, Nov 14, 2011 at 8:24 PM, Duncan Sands <baldrick
2011 Nov 14
0
[LLVMdev] Transferring value* in LLVM
On 14/11/11 19:20, Yakov Malinkovich wrote:
> I sure that is.
Did you test it? Can you do: src->getType()->isFloatTy()
What could be other reasons for such error?
The only other possibility I can think of is that src was created
using a different context.
Ciao, Duncan.
> Yakov
>
>
> On Mon, Nov 14, 2011 at 5:44 PM, Duncan Sands <baldrick at free.fr
>
2011 Nov 14
0
[LLVMdev] Transferring value* in LLVM
On 14/11/11 21:11, Yakov Malinkovich wrote:
> Here is the error that I get:
> Assertion failed: (i >= FTy->getNumParams() || FTy->getParamType(i) ==
> Params[i]->getType()) && "Calling a function with a bad signature!"
That's not being generated by the CreateCast, so it looks like your description
of the problem was quite misleading.
Ciao, Duncan.
>
2011 Nov 14
1
[LLVMdev] Transferring value* in LLVM
So what do you think the problem is?
Thank you.
Yakov
On Mon, Nov 14, 2011 at 10:20 PM, Duncan Sands <baldrick at free.fr> wrote:
> On 14/11/11 21:11, Yakov Malinkovich wrote:
>
>> Here is the error that I get:
>> Assertion failed: (i >= FTy->getNumParams() || FTy->getParamType(i) ==
>> Params[i]->getType()) && "Calling a function with a
2015 Jan 14
2
[LLVMdev] Bug in InsertElement constant propagation?
Hi,
When I run opt on the following LLVM IR:
define i32 @foo() {
bb0:
%0 = bitcast i32 2139171423 to float
%1 = insertelement <1 x float> undef, float %0, i32 0
%2 = extractelement <1 x float> %1, i32 0
%3 = bitcast float %2 to i32
ret i32 %3
}
->
It generates:
define i32 @foo() {
bb0:
ret i32 2143365727
}
While tracking the value I see that the floating point value
2011 Nov 14
2
[LLVMdev] Transferring value* in LLVM
I sure that is.What could be other reasons for such error?
Yakov
On Mon, Nov 14, 2011 at 5:44 PM, Duncan Sands <baldrick at free.fr> wrote:
> On 14/11/11 16:39, Yakov Malinkovich wrote:
>
>> It doesnt work it fails with assertation that cast is invalid .What
>> could be done?
>>
>
> Maybe src doesn't have Float type?
>
> Ciao, Duncan.
>
>
>
2019 Jul 01
14
RFC: Complex in LLVM
Hey all,
I volunteered to put together a proposal regard complex in LLVM.
Consider the following to be a strawman meant to spark discussion. It's
based on real-world experience with complex but is not expected to cover
all use-cases.
Proposal to Support Complex Operations in LLVM
----------------------------------------------
Abstract
Several vendors and individuals have proposed
2015 Jan 22
3
[LLVMdev] numeric limits of llvm Types?
Hi all,
can I access the numeric limits of the llvm types,
e.g. HalfTy, FloatTy, DoubleTy, etc.
in a fashion like the std numeric_limits tool?
std::numeric_limits<half>::min()
std::numeric_limits<half>::max()
In c++API, I want to initialize values and need to know the correct range
for the llvm types....
Thx
Alex
2015 Jan 14
2
[LLVMdev] Bug in InsertElement constant propagation?
Ha here is what I was missing. Thanks Jon. It still seems to me that the transformation of LLVM IR is invalid is that right? I assume we shouldn't be converting APFloat to float in order to avoid such problems?
-----Original Message-----
From: Jonathan Roelofs [mailto:jonathan at codesourcery.com]
Sent: Wednesday, January 14, 2015 9:39 AM
To: Raoux, Thomas F; LLVM Developers Mailing List
2015 Jan 20
2
[LLVMdev] Bug in InsertElement constant propagation?
Does anybody else have an opinion on this issue? I'm planning to submit a patch which would add a new get method for ConstantDataVector taking an ArrayRef<Constant*> and use that in the few places in constant propagation where convertToFloat is used.
Let me know if you think there is a more obvious way to do it.
Right now the only way to create a ConstantDataVector are those method:
2019 Aug 29
2
Complex proposal v2
All,
Here is the second revision of the proposal for a complex type in LLVM.
It clarifies a few things that came up during discussion and adds
additional operations for complex types.
-David
Proposal to Support Complex Operations in LLVM
----------------------------------------------
Revision History
v1 - Initial proposal [1]
v2 - This proposal
- Added complex of
2019 Oct 22
4
Complex proposal v3 + roundtable agenda
Ahead of the Wednesday’s roundtable at the developers’ conference, here is version three of
the proposal for first-class complex types in LLVM. I was not able to add Krzysztof Parzyszek’s
suggestion of a “cunzip” intrinsic returning two vectors as I could not find examples of intrinsics
that return two values at the IR level. The Hexagon intrinsics declared to return two values do
not actually
2020 Nov 12
0
Complex proposal v3 + roundtable agenda
Hi,
There’s growing interest among our users to make better use of dedicated hardware instructions for complex math and I would like to re-start the discussion on the topic. Given that this original thread was started a while ago apologies if I missed anything already discussed earlier on the list or the round-table. The original mail is quoted below.
In particular, I’m interested in the AArch64