Displaying 20 results from an estimated 1000 matches similar to: "[LLVMdev] Jello"
2004 Apr 01
3
[LLVMdev] 134.perl
Hi Chris,
It did compile when I gave that option. But it gives me an error
when I try to run the executable on an Intel machine.
-----
1513158 is not prime.
Exception handler needed, but not enabled. Recompile program with
-enable-correct-eh-support.
lli[0x8429bb4]
lli[0x8429dc0]
/lib/libc.so.6[0x40128c18]
/lib/libc.so.6(abort+0x161)[0x40129cb5]
[0x403da922]
../../../i386: line 4: 27606
2004 Apr 01
2
[LLVMdev] spec95
Ok, I am trying to configure llvm to compile benchmarks as suggested by
John, and after running configure, I get the following error while
running make in the /test/Programs/External/SPEC
----
make[1]: Entering directory
`/home/llvm/llvm/test/Programs/External/SPEC/CINT95'
make[2]: Entering directory
`/home/llvm/llvm/test/Programs/External/SPEC/CINT95/099.go'
2004 Apr 01
0
[LLVMdev] spec95
Vinay S. Belgaumkar wrote:
> Ok, I am trying to configure llvm to compile benchmarks as suggested by
> John, and after running configure, I get the following error while
> running make in the /test/Programs/External/SPEC
Hmmm. It sounds like the Makefiles are not creating the gccld command
line correctly.
Some questions:
1) Can you send us your Makefile.config?
2) Can you tell us
2004 Apr 01
1
[LLVMdev] Makefile.config
Hi John,
I have attached my Makefile.config.
I noticed that I did'nt have SRC_ROOT and OBJ_ROOT variables
defined as such in my environment. But I noticed that this is defined in
the Makefile.config by default to the same values.
All the same, I tried defining both these variables in my .cshrc, but I
still get the same error.
The main directory for me is /home/llvm, and I have
2004 Mar 31
1
[LLVMdev] 134.perl
Hello,
I am trying to compile 134.perl - the spec95 benchmark using LLVM and I
am getting the following error message -
--------------------------------------------
34.perl/symbol/dolist.c:1786: warning: "struct tm" declared inside parameter
list
134.perl/symbol/dolist.c:1786: warning: its scope is only this definition or
declaration, which is probably not what you want
2004 Apr 05
1
[LLVMdev] SSA
Sorry for the confusion, Misha seemed to answer my question in one way.
It'll be easier if I break down my question into parts -
- Is it possible to see the SSA form generated for my program ?
- Now, if this form is readable, is it in assembly code format ?
We want to look at the SSA form for any program and see if we can make
some changes ourselves to that format so that its reflected in
2004 Apr 05
1
[LLVMdev] CFG
Alright, I can now see my hammocks being translated into phi nodes.
Thanx for the info.
I now have a question regarding the analyze tool. I noticed it has a
-help option. I tried using the -print-cfg option. It creates a
cfg.main.dot file. Is there a graphical tool I can use to view this graph ?
Thanx,
--
Vinay S. Belgaumkar
2004 Apr 01
0
[LLVMdev] 134.perl
Vinay,
On Thu, Apr 01, 2004 at 02:27:53PM -0500, Vinay S. Belgaumkar wrote:
> It did compile when I gave that option. But it gives me an error
> when I try to run the executable on an Intel machine.
> -----
> 1513158 is not prime.
> Exception handler needed, but not enabled. Recompile program with
> -enable-correct-eh-support.
[snip]
This error message is from LLVM, not the
2003 Jul 31
2
[LLVMdev] Location of the x86 JIT compiler tool
Hi,
I'm mainly insterested on the x86 JIT compiler.
/lib/Target/X86/README.txt talks about 'Jello', the JIT compiler,
which should be on /tools/jello. I think that changed to /tools/lli
and now comprises a bytecode interpreter as well. Is that right?
--
Oscar
2012 Oct 03
2
[LLVMdev] LoopInfo analysis in CallGraphSCCPass
Hi,
Is it possible to recreate the LoopInfo analysis in my pass?
Thanks ,
Vinay
On Wed, Oct 3, 2012 at 2:34 PM, Chandler Carruth <chandlerc at google.com>wrote:
> This is not currently supported by the LLVM pass manager system. It is a
> serious deficiency that I (and others) would like to address, but it
> requires significant changes to the pass manager and analysis
2012 Oct 03
0
[LLVMdev] LoopInfo analysis in CallGraphSCCPass
On Wed, Oct 3, 2012 at 2:33 AM, vinay m <mvinay05041990 at gmail.com> wrote:
> Hi,
> Is it possible to recreate the LoopInfo analysis in my pass?
>
No. You need your pass to be a FunctionPass in order to use the LoopInfo
(and associated) analyses.
>
> Thanks ,
> Vinay
>
> On Wed, Oct 3, 2012 at 2:34 PM, Chandler Carruth <chandlerc at google.com>wrote:
2010 Feb 05
2
Segmentation Fault while compiling and installing openssh-3.9p1
I am trying to compile and install openssh-3.9p1 (with openssl-0.9.7j)
on my personal dev env to have a play. I get the below mentioned
segmentation fault message.
---------
Generating public/private rsa1 key pair.
/bin/sh: line 1: 10901 Segmentation fault ./ssh-keygen -t rsa1 -f
/home/vinay/var/vinay_ssh/etc/ssh_host_key -N ""
Generating public/private dsa key pair.
/bin/sh: line
2014 Mar 27
3
arm64 support
I have used the patch to build opus 1.1. Although I have not tried the
latest git master, will try that. Will that work for armv7, armv7s and
arm64?
On Wed, Mar 26, 2014 at 11:01 PM, Martin Storsj? <martin at martin.st> wrote:
> On Wed, 26 Mar 2014, Jonathan Lennox wrote:
>
>
>> On Mar 26, 2014, at 7:55 AM, Peter Robinson <pbrobinson at gmail.com> wrote:
>>
2009 Feb 23
2
[LLVMdev] make-test dependencies on local directory
Hi,
I am getting this when running make-test :-
$ /usr/src/llvm-test-2.5/configure
checking for spec95 benchmark sources... no, not found in
/home/vadve/shared/ben
chmarks/spec95/benchspec
checking for spec2000 benchmark sources... no, not found in
/home/vadve/shared/b
enchmarks/speccpu2000/benchspec
checking for spec2006 benchmark sources... no, not found in
/home/vadve/shared/b
2005 Jul 22
2
[LLVMdev] Need help on SPEC 95 "standard" commandlines
Some of the run commandlines don't seem to be the *default ref*
configuration. For instance, in 099.go, what's in the script is:
LEVEL = ../../../..
BM=099.go
ifeq ($(RUN_TYPE),test)
STDIN_FILENAME = /dev/null
STDOUT_FILENAME = null.out
RUN_OPTIONS = 40 19
else
STDIN_FILENAME = 2stone9.in
STDOUT_FILENAME = 2stone9.out
RUN_OPTIONS = 50 9
endif
include ../../Makefile.spec95
2005 Jul 22
2
[LLVMdev] Need help on SPEC 95 "standard" commandlines
Does anyone know the "standard" commandline to compile and run spec95
benchmarks ?
I found some scripts in llvm test suite (External/SPEC/CINT95), but I am
not sure if they are the *default ref* configurations. <Some of them
seem to use smaller problem sizes.> SPEC95 was retired many years ago,
so few people around me know how to compile and run them.
I am building from
2014 Mar 27
1
arm64 support
I am trying to generate the config and makefiles using ./autogen.sh on the
mac but get the following error:
Can't exec "aclocal": No such file or directory at
/usr/local/share/autoconf/Autom4te/FileUtils.pm line 326.
autoreconf: failed to run aclocal: No such file or directory
How do I build opus from source? Am I missing some step?
On Thu, Mar 27, 2014 at 11:29 AM, Vinay Nair
2009 Feb 23
2
[LLVMdev] make-test dependencies on local directory
On Mon, Feb 23, 2009 at 6:09 PM, Dale Johannesen <dalej at apple.com> wrote:
> These benchmarks are not distributed with llvm (which doesn't have the
> legal right to distribute Spec, for example). If you have them from
> another source, you need to configure --with-externals=<path>
Okay, thanks. Thre should be better warning/error reporting though.
Aaron
>
>
2014 Mar 26
2
arm64 support
On Mar 26, 2014, at 7:55 AM, Peter Robinson <pbrobinson at gmail.com> wrote:
> On Wed, Mar 26, 2014 at 11:45 AM, Vinay <vinay.nair at novanet.net> wrote:
>> Hi,
>>
>> I wanted to build opus along with PJSIP for iOS for the architecture arm64.
>> I wanted to know if opus supports arm64?
>
> The opus code builds fine on ARM64 on Linux at least,
2005 Jul 22
0
[LLVMdev] Need help on SPEC 95 "standard" commandlines
On Thu, 21 Jul 2005, Long Fei wrote:
> which suggests the compiling command:
> gcc -DSPEC_CPU95 -O2 -o spec_go g2.c g22.c g23.c g25.c g26.c g27a.c g27b.c
> g28.c g29.c g2eye.c g2jlib2.c g2jos.c g2list.c g2reas.c g2s2.c g2s3.c g2shp.c
> and the running commandline:
> ./spec_go 50 9 2stone9.in
> < are these correct ? >
I believe that we only include test/train inputs for