Displaying 20 results from an estimated 32 matches for "isintegerti".
Did you mean:
isintegerty
2015 Jan 22
2
[LLVMdev] access IntegerType::getSignBit from Type *
Hi,
I have a Type * which may come from an IntegerType as shown below:
Type.getIntegerBitWidth() tells me numBits.
But how to extract the IntegerType.getSignBit?
If pType isIntegerType, I need to know if it is signed or unsigned...
How to achieve this?
Thx
Alex
llvm::Type * getRandomValid_IntegerType(llvm::LLVMContext &C)
{
using namespace llvm;
//--- determine num of bits
2017 Jan 31
2
Folding zext from i1 into PHI nodes with only zwo incoming values.
Hi Sanjay,
2017-01-30 22:22 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
> My minimal patch idea is to ease the restriction in ShouldChangeType
> because i1 is special. I tried the patch below, and it works on the
> example...and nothing in 'make check' failed. :)
>
Yeah, that would work for me as well, I just wasn't sure about the
implications that has.
2013 Feb 25
2
[LLVMdev] Queries regarding function's arguments data type
Hi all,
I am working on my Master's project in security and I am trying to iterate
over the argument list of the function. Basically I need to do following
things :
1. Check data type of each argument of the argument list of the function.
2. Based on its data type like character array or integer array, pointer,
int, char, take different action.
3. I have added following code to check its
2011 Jun 06
2
[LLVMdev] Explanation
Hi All,
I am trying to check if a Value type is a int32 pointer by using
if(T == Type::getInt1PtrTy(Context, AS)) ...
I am trying to understand the AS (address space).
How do I get it? Thanks.
George
*
*
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20110606/775e4f09/attachment.html>
2011 Jun 06
0
[LLVMdev] Explanation
On 6 June 2011 17:08, George Baah <georgebaah at gmail.com> wrote:
> if(T == Type::getInt1PtrTy(Context, AS)) ...
Hi,
You don't need to care about address spaces to check for an int32*:
if (T->isPointerTy()) {
const Type* intT = cast<PointerType>(T)->getElementType();
if (intT->isIntegerTy() && intT->getPrimitiveSizeInBits() == 32)
cout <<
2011 Jun 06
1
[LLVMdev] Explanation
On Jun 6, 2011, at 10:05 AM, Renato Golin wrote:
> On 6 June 2011 17:08, George Baah <georgebaah at gmail.com> wrote:
>> if(T == Type::getInt1PtrTy(Context, AS)) ...
>
> You don't need to care about address spaces to check for an int32*:
>
> if (T->isPointerTy()) {
> const Type* intT = cast<PointerType>(T)->getElementType();
> if
2017 Jan 31
0
Folding zext from i1 into PHI nodes with only zwo incoming values.
On Tue, Jan 31, 2017 at 3:09 AM, Björn Steinbrink <bsteinbr at gmail.com>
wrote:
> Hi Sanjay,
>
> 2017-01-30 22:22 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
>
>> My minimal patch idea is to ease the restriction in ShouldChangeType
>> because i1 is special. I tried the patch below, and it works on the
>> example...and nothing in 'make
2017 Jan 31
1
Folding zext from i1 into PHI nodes with only zwo incoming values.
2017-01-31 16:59 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
>
>
> On Tue, Jan 31, 2017 at 3:09 AM, Björn Steinbrink <bsteinbr at gmail.com>
> wrote:
>
>> Hi Sanjay,
>>
>> 2017-01-30 22:22 GMT+01:00 Sanjay Patel <spatel at rotateright.com>:
>>
>>> My minimal patch idea is to ease the restriction in ShouldChangeType
2013 Feb 25
0
[LLVMdev] Queries regarding function's arguments data type
On 2/25/13 1:44 PM, teja tamboli wrote:
> Hi all,
>
> I am working on my Master's project in security and I am trying to
> iterate over the argument list of the function. Basically I need to do
> following things :
Interesting. Just out of curiosity, can you tell us what your project
is about?
>
> 1. Check data type of each argument of the argument list of the
2015 Mar 10
4
[LLVMdev] n-bit bytes for clang/llvm
Back in 2009 there was some discussion of the practicality of supporting
char sizes greater than 8-bit:
http://lists.cs.uiuc.edu/pipermail/cfe-dev/2009-September/thread.html#6349
http://lists.cs.uiuc.edu/pipermail/llvmdev/2009-September/thread.html#26025
with the consensus seemingly being "quite doable, please get a good patch
and submit".
However the current code appears (to my
2017 Jan 30
0
Folding zext from i1 into PHI nodes with only zwo incoming values.
Hi Björn and Daniel,
FoldPHIArgOpIntoPHI() is for unary ops (casts), but it calls
FoldPHIArgBinOpIntoPHI() for binops which takes care of almost everything
else?
My minimal patch idea is to ease the restriction in ShouldChangeType
because i1 is special. I tried the patch below, and it works on the
example...and nothing in 'make check' failed. :)
Index:
2015 Oct 12
2
question about llvm partial unrolling/runtime unrolling
Hi,
I am trying to do loop unrolling with loops that don't have constant loop
counter. It is highly appreciated if anyone can help me on this.
What I want to do is to turn
loop (n)
{
<loop body>
}
into
loop (n/4)
{
<loop body>
<loop body>
<loop body>
<loop body>
}
loop (n%4)
{
<loop
2017 Aug 07
2
vrp
On Mon, Aug 7, 2017 at 2:14 AM, Anastasiya Ruzhanskaya via llvm-dev
<llvm-dev at lists.llvm.org> wrote:
> I am trying to print it like this (maybe here is smth wrong?)
>
>
> LazyValueInfo &LV = getAnalysis<LazyValueInfoWrapperPass>().getLVI();
> DominatorTree &DT =
> getAnalysis<DominatorTreeWrapperPass>().getDomTree();
> LV.printLVI(F,
2017 Jan 30
3
Folding zext from i1 into PHI nodes with only zwo incoming values.
Hi Sanjay,
unfortunately that patch does not help in my case. Here's the IR that fails
to get fully optimized:
target datalayout = "e-m:e-i64:64-f80:128-n8:16:32:64-S128"
target triple = "x86_64-unknown-linux-gnu"
define fastcc zeroext i1 @testfunc(i8** noalias nocapture readonly
dereferenceable(8)) unnamed_addr {
entry-block:
%1 = load i8*, i8**
2010 Apr 22
1
[LLVMdev] 2.7 release notes
Thanks, I must have missed these, added.
On Apr 22, 2010, at 1:28 AM, Matthieu Moy wrote:
> Chris Lattner <clattner at apple.com> writes:
>
>> Ok, the LLVM 2.7 release notes are in near final shape. Please take
>> a look and suggest improvements (or, better yet, just commit
>> improvements if you have commit access):
>
> About the API changes, some that hit
2017 Aug 07
2
vrp
I am primarily interested in phi nodes and their induction variables, in
ValueTracking file there is an analysis of them, but if the upper bound is
inf, it is not working?
2017-08-07 11:41 GMT+02:00 Anastasiya Ruzhanskaya <
anastasiya.ruzhanskaya at frtk.ru>:
> So, it is not supported to determine by this instruction : %cmp = icmp slt
> i32 %i.03, 99,
> that %i.03 = phi i32 [ 0,
2010 Apr 22
0
[LLVMdev] 2.7 release notes
Chris Lattner <clattner at apple.com> writes:
> Ok, the LLVM 2.7 release notes are in near final shape. Please take
> a look and suggest improvements (or, better yet, just commit
> improvements if you have commit access):
About the API changes, some that hit me when I ported some code to
LLVM 2.7, and not in the release notes (I had sent a private email
some time ago) :
---
2015 Oct 16
2
question about llvm partial unrolling/runtime unrolling
Hi Hal,
I did
opt.exe -S -debug -loop-unroll -unroll-runtime=true -unroll-count=4
csShader.ll
and it prints out:
Args: opt.exe -S -debug -loop-unroll -unroll-runtime=true -unroll-count=4
csShader.ll
Loop Unroll: F[build_cs_5_0] Loop %loop_entry
Loop Size = 82
partially unrolling with count: 1
Thanks,
Frances
On Thu, Oct 15, 2015 at 9:35 PM, Hal Finkel <hfinkel at anl.gov>
2017 Aug 07
2
vrp
Hello,
I am trying to figure out, what vrp propagation does in llvm. I tried this
program:
#include <stdio.h>
int main() {
int s = 0;
int j = 0;
for (int i = 0; i < 100; i++) {
j = j+i+1;
s+=j;
}
return (s+j);
}
And got this under optimized version ( I don't want everything to be
eliminated)
define i32 @main()
2015 Mar 11
3
[LLVMdev] n-bit bytes for clang/llvm
> It's definitely doable, but I'd be worried about the maintenance burden.
Yes, that is a problem.
We are currently not allowed to reveal our target (which has 16-bit bytes, and registers with non-power-of-two bit widths) fully, and therefore not able to submit it upstream. One idea we have toyed with is to create a simple "dummy" version of our target, just to be able