Displaying 20 results from an estimated 5000 matches similar to: "[LLVMdev] multithreaded applications"
2009 Feb 03
0
[LLVMdev] multithreaded applications
On Tue, Feb 3, 2009 at 12:33 PM, aparna kotha <kotha.aparna at gmail.com> wrote:
> Hi all:
>
> I am working on a project using llvm and we need to deal with multithreaded
> applications. I wanted to know if there was a C front end for llvm that
> could parse multithreaded applications? I tried llvm-gcc (4.2) and could not
> get it to work. Is there an extra parameter that I
2009 Feb 03
2
[LLVMdev] multithreaded applications
I am using pthreads.
I was also wondering what will the llvm IR be for pthreads ?
On Tue, Feb 3, 2009 at 3:51 PM, Bill Wendling <isanbard at gmail.com> wrote:
> On Tue, Feb 3, 2009 at 12:33 PM, aparna kotha <kotha.aparna at gmail.com>
> wrote:
> > Hi all:
> >
> > I am working on a project using llvm and we need to deal with
> multithreaded
> >
2009 Feb 03
0
[LLVMdev] multithreaded applications
On Tue, Feb 3, 2009 at 12:55 PM, aparna kotha <kotha.aparna at gmail.com> wrote:
> I am using pthreads.
>
> I was also wondering what will the llvm IR be for pthreads ?
>
Okay. Luke gave hints on how to get pthreads to work. LLVM doesn't do
anything special for pthreads calls. So they should look like regular
calls into a library.
-bw
2013 Mar 03
3
[LLVMdev] AESOP autoparallelizing compiler
Hi Sebastian,
Sure! The bulk of LMDA was written by Aparna Kotha (CCd). It computes dependences between all instructions, computes the resulting direction vectors in the function, then associates them all with loops.
At a high level, the dependence analysis consults with AliasAnalysis, and ScalarEvolution before resorting to attempting to understand the effective affine expressions and
2013 Mar 03
0
[LLVMdev] AESOP autoparallelizing compiler
----- Original Message -----
> From: "Timothy Mattausch Creech" <tcreech at umd.edu>
> To: "Sebastian Dreßler" <dressler at zib.de>
> Cc: "Aparna Kotha" <akotha at umd.edu>, llvmdev at cs.uiuc.edu
> Sent: Sunday, March 3, 2013 11:32:49 AM
> Subject: Re: [LLVMdev] AESOP autoparallelizing compiler
>
> Hi Sebastian,
> Sure!
2009 Apr 13
2
[LLVMdev] generation of shared libraries.
Thanks a lot.
A see the shared library in linux version. I initially tried doing this in
cygwin where I dont see the shared library being built. Do u think it could
have been cygwin that is the problem?
Aparna
On Mon, Apr 13, 2009 at 5:16 PM, Milos Puzovic <milos.puzovic at gmail.com>wrote:
> In order to generate shared libraries you need to have SHARED_LIBRARY
> and
2009 Mar 18
4
[LLVMdev] decimal to floating point conversion
Hi all:
I need an instruction that can convert decimal values into floating point
numbers.
i.e. say I have a decimal number 1110794174 (== 42355FBE in hex ) and (==
45.3435 as a float)
essentially the mantissa and exponent representation needs to be used.
Is there any way of doing this in llvm?
Thanks and Regards
--
-- Aparna Kotha
Graduate Student
Electrical and Computer Engineering
2009 Apr 13
0
[LLVMdev] generation of shared libraries.
I believe because cygwin behaves like windows (it is just a posix
layer over window) it doesn't have dynamic linking hence only static
libraries have been built.
On 13 Apr 2009, at 23:16, aparna kotha wrote:
> Thanks a lot.
>
> A see the shared library in linux version. I initially tried doing
> this in cygwin where I dont see the shared library being built. Do
> u
2010 Aug 13
1
[LLVMdev] Pass Ordering
I am using opt , so i cm confused if i need to do this. On the other hand I
modified my functionPass not to call TargetData , and I still get this
error. My functionPass still calls Alias Analysis though.
Aparna
On Fri, Aug 13, 2010 at 2:15 PM, John Criswell <criswell at illinois.edu>wrote:
> aparna kotha wrote:
>
>> All,
>> I have a ModulePass (A) calling a
2009 Apr 13
2
[LLVMdev] generation of shared libraries.
I am trying to run the LLVM hello world pass. I observe that in the
OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are generated. But
I am confused as to how to generate the .so library file from here.
I am kinda new to compilers and hence the question I know is basic , but
couldnt figure the answer out myself.
Thanks a lot for your help.
Regards
--
-- Aparna Kotha
Research
2010 Aug 13
2
[LLVMdev] Pass Ordering
All,
I have a ModulePass (A) calling a FunctionPass that inturn calls TargetData
(a ModulePass). For reasons of code correctness and modularity I cannot
reorganize my passes in any other way .
When I use opt to load and run A , it gives the following error.
LLVM ERROR: Bad TargetData ctor used. Tool did not specify a TargetData to
use?
I gather from some previous emails that this was not
2009 Apr 13
0
[LLVMdev] generation of shared libraries.
In order to generate shared libraries you need to have SHARED_LIBRARY
and LOADABLE_MODULE defined in the Makefile. See here for more
details: http://llvm.org/docs/MakefileGuide.html#libraries
On 13 Apr 2009, at 20:46, aparna kotha wrote:
> I am trying to run the LLVM hello world pass. I observe that in the
> OUPUT_DIR/lib the LLVMHello.a and LLVMHello.la libraries are
>
2009 Oct 30
1
[LLVMdev] llvm-gcc
This is the name of a structure in the source code.
2009/10/30 Török Edwin <edwintorok at gmail.com>
> On 2009-10-30 19:41, aparna kotha wrote:
> > We are trying to compile a .c file using llvm-gcc --emit-llvm .
> >
> > The produced output has a variable name different from its name in the
> > .c file. We have tried it on different llvm-gcc versions and
2010 Aug 13
0
[LLVMdev] Pass Ordering
aparna kotha wrote:
> All,
>
> I have a ModulePass (A) calling a FunctionPass that inturn calls
> TargetData (a ModulePass). For reasons of code correctness and
> modularity I cannot reorganize my passes in any other way .
>
> When I use opt to load and run A , it gives the following error.
>
> LLVM ERROR: Bad TargetData ctor used. Tool did not specify a
>
2011 May 25
2
[LLVMdev] Floating Point Register Allocation in X86 backend
Right. But there are 8 registers on the floating point stack from ST0 to ST7
and I think llvm is only using ST0 to ST6 in some code fragments. Could this
be because of the assumption that X86::FP registers run from X86::FP0 to
X86:FP6 ?
--Aparna
On Wed, May 25, 2011 at 2:28 PM, Jakob Stoklund Olesen <stoklund at 2pi.dk>wrote:
>
> On May 25, 2011, at 11:09 AM, aparna kotha wrote:
2011 May 25
2
[LLVMdev] Floating Point Register Allocation in X86 backend
Hi Guys,
I was working on some floating point intensive benchmarks and realize that
the floating point register allocation in llvm assumes that there are only 7
floating point registers in X86, whereas the hardware has 8.
Line number
00266 assert(Reg >= X86::FP0 && Reg <= X86::FP6 && "Expected FP register!");
of X86FloatingPoint.cpp.
Is there any reason for
2009 Feb 17
3
[LLVMdev] FP128Ty
I am new to llvm and am stuck up with a problem.
I am trying to initialize a Value* of type fp128 having the value 0
I am using the following construct
ConstantFP::get(APFloat(APInt(128,0,false)));
This is returning a double instead of a float and I am confused.
Thanks a lot for your help.
--
-- Aparna
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Oct 30
2
[LLVMdev] llvm-gcc
We are trying to compile a .c file using llvm-gcc --emit-llvm .
The produced output has a variable name different from its name in the .c
file. We have tried it on different llvm-gcc versions and different
optimization levels.
Is there any reason that this happens.
Aparna
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
2009 Mar 18
0
[LLVMdev] decimal to floating point conversion
aparna kotha wrote:
> Hi all:
>
> I need an instruction that can convert decimal values into floating
> point numbers.
>
> i.e. say I have a decimal number 1110794174 (== 42355FBE in hex ) and
> (== 45.3435 as a float)
>
> essentially the mantissa and exponent representation needs to be used.
>
>
> Is there any way of doing this in llvm?
I think
2011 May 25
0
[LLVMdev] Floating Point Register Allocation in X86 backend
On May 25, 2011, at 11:09 AM, aparna kotha wrote:
> Hi Guys,
>
> I was working on some floating point intensive benchmarks and realize that the floating point register allocation in llvm assumes that there are only 7 floating point registers in X86, whereas the hardware has 8.
>
> Line number
> 00266 assert(Reg >= X86::FP0 && Reg <= X86::FP6 &&