Displaying 20 results from an estimated 39 matches for "alenhar2".
2007 Nov 02
3
[LLVMdev] [Fwd: Fwd: LLVM and threading]
Dear All,
Here's a question Vikram and I received. Is the LLVM JIT thread safe?
-- John T.
-------------- next part --------------
An embedded message was scrubbed...
From: "Adve, Vikram Sadanand" <vadve at uiuc.edu>
Subject: Fwd: LLVM and threading
Date: Thu, 1 Nov 2007 09:48:59 -0500
Size: 3037
URL:
2005 May 14
0
[LLVMdev] debian
On Sat, May 14, 2005 at 02:18:26AM +0200, Stefan Strasser wrote:
> in case you're interested in having llvm in debian sarge: it was
> removed today. I don't know why, but you might want to find out
> because sarge is in freeze phase for release next month.
Possibly because of these:
http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=llvm
I addressed the first one and fixed it in
2005 Feb 27
0
[LLVMdev] Problem in compilation (native option)
Thanks for replying .
I came across another problem while trying it.
The following compilation is not working: ( with the native option)
llvmgcc x.c -o a.out -Wl,-native
I get this error:
gccld: a.out.s: Can't destroy file: ut.s
How can I fix that ?
Thanks
Tanu
Andrew Lenharth <alenhar2 at cs.uiuc.edu> wrote:
On Sat, 2005-02-26 at 22:34 -0600, Chris Lattner wrote:
> On Sat, 26 Feb 2005, Tanu Sharma wrote:
>
> > Thanks for the reply :-)
> > I am actually looking for ways to determine "size" of code segment when the program is in native code.
> >...
2005 May 14
3
[LLVMdev] debian
in case you're interested in having llvm in debian sarge: it was removed
today. I don't know why, but you might want to find out because sarge is
in freeze phase for release next month.
regards,
--
Stefan Strasser
2005 Feb 27
2
[LLVMdev] Measuring performance overhead
On Sat, 2005-02-26 at 22:34 -0600, Chris Lattner wrote:
> On Sat, 26 Feb 2005, Tanu Sharma wrote:
>
> > Thanks for the reply :-)
> > I am actually looking for ways to determine "size" of code segment when the program is in native code.
> > Any suggestions to do that ?
>
> Compile it with llvm to a native .o or .exe file, then run 'size' on it?
>
2008 Nov 24
0
[LLVMdev] how to track down a kernel miscompilation?
For people who want to try hacking on the linux kernel with llvm, here
is a head start:
http://llvm.org/~alenhar2/k.tbz
This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio
devices (I also think it will work with the default devices). The
build process uses llvm-gcc -> opt -> llc so you can add your own
(per-file) passes to the build process or debug specific passes.
Directories arch...
2008 Nov 24
1
[LLVMdev] how to track down a kernel miscompilation?
...ter allocator used, but is otherwise
seems stable for a given configuration.
Andrew
On Mon, Nov 24, 2008 at 10:53 AM, Andrew Lenharth <andrewl at lenharth.org> wrote:
> For people who want to try hacking on the linux kernel with llvm, here
> is a head start:
>
> http://llvm.org/~alenhar2/k.tbz
>
> This is a 2.6.27.5 kernel with a .config file for qemu/kvm with virtio
> devices (I also think it will work with the default devices). The
> build process uses llvm-gcc -> opt -> llc so you can add your own
> (per-file) passes to the build process or debug specific p...
2005 Jun 17
1
[LLVMdev] varargs heads up
...d PPC (not the default codegen, so shouldn't
really affect anybody)
If you read a .ll or .bc file it will be converted to the new format and
any file written will use the new instructions and intrinsics. And yes,
the conversion produces horibly ugly code, but oh well.
--
Andrew Lenharth <alenhar2 at cs.uiuc.edu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20050617/65c40ef1/attachme...
2005 Jun 01
3
[LLVMdev] 64-bit Linux Support
Hi!
What's the plan for support on Linux 64-bit machines? Is that actively
being worked on right now or is there a roadmap for doing this?
Thanks!
-bw
2005 May 14
2
[LLVMdev] debian
...ues that I'm not quite
> following.
(CCing the bug and thus the submitter)
sounds like a missing built-depends, at least graphviz, possibly
something else. Could you give us some of the error output from your
build to help narrow things down?
Thanks
Andrew Lenharth
andrewl at debian.org
alenhar2 at cs.uiuc.edu
2005 Feb 28
1
[LLVMdev] Problem in compilation (native option)
...ilation is not working: ( with the native option)
>
> llvmgcc x.c -o a.out -Wl,-native
>
> I get this error:
>
> gccld: a.out.s: Can't destroy file: ut.s
>
> How can I fix that ?
This bug has been fixed in CVS, please update your tree.
-Chris
> Andrew Lenharth <alenhar2 at cs.uiuc.edu> wrote:
> On Sat, 2005-02-26 at 22:34 -0600, Chris Lattner wrote:
>> On Sat, 26 Feb 2005, Tanu Sharma wrote:
>>
>>> Thanks for the reply :-)
>>> I am actually looking for ways to determine "size" of code segment when the program is in nat...
2009 Aug 24
3
[LLVMdev] Request Permission for approve-after-commit for Profiling Infrastructure.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
since I'm planing on a whole bunch of changes in the area of the
Profiling Infrastructure I would like to ask humbly if it is possible to
have approve-after-commit permission for the following files:
include/llvm/Analysis/ProfileInfo.h
include/llvm/Analysis/ProfileInfoLoader.h
include/llvm/Analysis/ProfileInfoTypes.h
2005 Dec 02
1
[LLVMdev] RFC: Plugable intrinsics
...smaller context
like research and make it much easier to try out extentions before
considering them for inclusion in LLVM.
I have talked to several people (both in my group and out) who maintain
out of tree intrinsics and they univerally think this would be a good
idea :)
--
Andrew Lenharth <alenhar2 at uiuc.edu>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20051202/269c3551/attachment....
2005 May 05
0
[LLVMdev] Scheme + LLVM JIT
...itude) if one makes a release
build (make ENABLE_OPTIMIZED=1)
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
>
>
--
Andrew Lenharth <alenhar2 at cs.uiuc.edu>
--
Andrew Lenharth <andrewl at lenharth.org>
2008 Nov 24
4
[LLVMdev] how to track down a kernel miscompilation?
Hi,
I am trying to build the Linux kernel with LLVM.
'ARCH=um' appears to work, now I am trying to get 'ARCH=x86' to work.
So far it seems there is something wrong with the boot vga code (it
finds no video modes), the acpi code, and the serial console code.
I am now trying to compile drivers/ with llvm-gcc and the rest with
gcc-4.2 (I have a wrapper script), I am compiling to
2005 Aug 29
1
[LLVMdev] Re: Forward of moderated message
llvm-bounces at cs.uiuc.edu wrote:
>
> ------------------------------------------------------------------------
>
> Subject:
> Fw: (by sospeng at tom.com)something is wrong , when compiling llvm on debian
> From:
> "4" <sospeng at tom.com>
> Date:
> Mon, 29 Aug 2005 20:05:46 +0800 (CST)
> To:
> llvmdev at cs.uiuc.edu
>
> To:
> llvmdev at
2005 Oct 11
10
[LLVMdev] Next LLVM release thoughts?
Hi All,
It has been entirely too long since the last release, and we have plenty
of goodies for a very solid release. Do people find releases useful, or
should we just continue to run out of CVS? Does anyone have any thoughts?
-Chris
--
http://nondot.org/sabre/
http://llvm.org/
2005 May 05
4
[LLVMdev] Scheme + LLVM JIT
Hi List,
I am in the preliminary stages of adding a JIT compiler to a sizable
Scheme system (PLT Scheme). The original plan was to use GNU
Lightning, but 1) it seems to be dead, and 2) LLVM has already done a
huge amount of stuff that I would have had to write (poorly) from
scratch.
At the moment, LLVM seems to be the ideal choice for implementing the
Scheme JIT, but there are problems that need
2010 Mar 09
0
[LLVMdev] Fwd: help with llvm-convert
On alpha, I am seeing a problem with Emiting va_copy. valists are
structs and allocated by alloca, unlike x86. EmitBuiltinVACopy is
therefore using the second branch of the if (~llvm-convert.cpp:6538)
to emit the second argument. The second argument is the result of an
alloca. TreeToLLVM::Emit is hitting the first assertion (~929).
The exp being passed is:
<var_decl 0x20000b44240 ap
2005 Mar 10
1
[LLVMdev] new llvm-testresults mailing list
On Thu, 2005-03-10 at 04:13, Vladimir Merzliakov wrote:
> Also I found some inconsistent at http://llvm.cs.uiuc.edu/testresults/ page:
> all hardware platform names is bold except Alpha.
Really? Are you sure? ;)
Andrew