Displaying 20 results from an estimated 3000 matches similar to: "[LLVMdev] Size and performance figures for LLVM?"
2008 May 12
0
[LLVMdev] Size and performance figures for LLVM?
On May 12, 2008, at 2:59 AM, Pertti Kellomäki wrote:
> 2) What is the relative performance of code generated by LLVM
> and gcc respectively?
See llvm.org/nightlytest Many testers run various benchmarks and
produces comparison numbers daily.
> I am not looking for exact answers, rough ballpark figures
> are quite sufficient.
-
Devang
2008 May 12
2
[LLVMdev] Size and performance figures for LLVM?
Am Montag, den 12.05.2008, 09:08 -0700 schrieb Devang Patel:
> On May 12, 2008, at 2:59 AM, Pertti Kellomäki wrote:
>
> > 2) What is the relative performance of code generated by LLVM
> > and gcc respectively?
>
> See llvm.org/nightlytest
Which does not compare GCC vs. LLVM. (I haven't seen this announced as
the nightly tester's purpose either.)
> Many
2008 May 13
2
[LLVMdev] Size and performance figures for LLVM?
> See llvm.org/nightlytest Many testers run various benchmarks
> and produces comparison numbers daily.
Can I trust those numbers? For example, right now I'm looking at
http://llvm.org/nightlytest/machine.php?machine=230.
"CVS checkout time" might be wrong, as LLVM is now in SVN.
This column also jitters heavily. However, it's not really
important.
"Configure
2008 May 12
0
[LLVMdev] Size and performance figures for LLVM?
On May 12, 2008, at 10:19 AM, Joachim Durchholz wrote:
>
> Am Montag, den 12.05.2008, 09:08 -0700 schrieb Devang Patel:
>> On May 12, 2008, at 2:59 AM, Pertti Kellomäki wrote:
>>
>>> 2) What is the relative performance of code generated by LLVM
>>> and gcc respectively?
>>
>> See llvm.org/nightlytest
>
> Which does not compare GCC vs. LLVM.
2008 May 13
4
[LLVMdev] Size and performance figures for LLVM?
Am Montag, den 12.05.2008, 10:48 -0700 schrieb Chris Lattner:
> On May 12, 2008, at 10:19 AM, Joachim Durchholz wrote:
>
> >
> > Am Montag, den 12.05.2008, 09:08 -0700 schrieb Devang Patel:
> >> On May 12, 2008, at 2:59 AM, Pertti Kellomäki wrote:
> >>
> >>> 2) What is the relative performance of code generated by LLVM
> >>> and gcc
2006 Nov 09
2
[LLVMdev] LLVM and newlib progress
Hi Reid,
I'll write a separate post about the intrinsics, but just
a quick note about the CFLAGS issue.
Reid Spencer kirjoitti:
> On Thu, 2006-11-09 at 15:29 +0200, Pertti Kellomäki wrote:
>> Another related thing is that even when I defined -emit-llvm in
>> what I thought would be a global CFLAGS for all of newlib, it did
>> not get propagated to all subdirectories.
2006 Apr 20
0
[LLVMdev] 1.7 Pre-Release Ready for Testing
This came up when trying to compile the Python bindings
against llvm 1.7. File include/llvm/Transforms/Scalar.h
declares llvm::createPREPass(), which does not seem to
be implemented anywhere. Should I report this in llvmbugs?
--
Pertti
2008 Oct 15
6
[LLVMdev] LLVM 2.4 problem? (resend)
On 15.10.2008, at 14.01, Pertti Kellomäki wrote:
> Tatu Vaajalahti wrote:
>> With this program llvm-gcc -O2 optimizes test2 away even though it's
>> address is taken in program (gcc-4.2 does not, neither does llvm-gcc
>> with -O or -O0):
>>
>>
>> #include <stdio.h>
>>
>> static const char test1 = 'x';
>> static const char
2006 Apr 20
1
[LLVMdev] 1.7 Pre-Release Ready for Testing
Pertti Kellomäki wrote:
> This came up when trying to compile the Python bindings
> against llvm 1.7. File include/llvm/Transforms/Scalar.h
> declares llvm::createPREPass(), which does not seem to
> be implemented anywhere. Should I report this in llvmbugs?
Just to clarify myself: this is an issue with the LLVM sources,
not with the Python bindings.
--
Pertti
2008 Oct 15
0
[LLVMdev] LLVM 2.4 problem? (resend)
Tatu Vaajalahti wrote:
> On 15.10.2008, at 14.01, Pertti Kellomäki wrote:
>> Seems to me that it is perfectly legitimate for the compiler to fold
>> the two char constants together.
> True, but note that it is the address of a variable that is used, not
> the value.
I don't have the C standard handy, but I would be somewhat
surprised if the standard would explicitly
2009 Apr 22
4
[LLVMdev] Strange loop unrolling problem
I am having a strange problem with loop unrolling. Attached is
a small example that demonstrates what happens.
There is a for-loop with a known trip count, and some control
flow inside the loop. If the condition of the control flow only
depends on the loop index and loop invariant variables, the loop
is not unrolled. However, if the condition involves potentially
loop variant variables, the loop
2006 Nov 23
3
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
On Wed, 22 Nov 2006, [ISO-8859-1] Pertti Kellom�ki wrote:
> Aside from stuff that depends on system headers, are there any other
> dependencies on the host system? In other words, will llvm-gcc produce
> exactly the same byte code for a given set of source files regardless of
> where compilation takes place? This has obvious implications on
Yes. Many aspects of the target compiler
2009 Jun 04
0
[LLVMdev] LLVM frontend supporting arbitrary bit-width integral datatypes
Hi Adam,
John is right, the TCE stuff would be useful for you. Our
compiler targets a processor template that the designer can
populate pretty freely. The compiler then reads the architecture
description and creates an LLVM backend on the fly.
Please don't hesitate to get in touch with us if you have
questions.
--
Pertti
2006 Nov 23
2
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
Pertti Kellomäki schrieb:
> Chris Lattner wrote:
>> Many aspects of the target compiler can leak through.
>
> So if one wants to use the LLVM system as a cross compiler, one
> has to configure llvm-gcc as a cross compiler? Fair enough, I guess.
I hope the C backend is still meant to generate portable code though.
Philipp
2006 Nov 09
9
[LLVMdev] LLVM and newlib progress
I managed to compile newlib with llvm-gcc yesterday. That
is, the machine independent part is now basically done, and
the syscall part contains no-op stubs provided by libgloss.
I haven't tested the port yet, but since newlib has already
been ported to many architectures, I would be pretty surprised
if there were any major problems.
A couple of things I noticed when configuring newlib for
2006 Nov 23
0
[LLVMdev] Byte code portability (was Re: libstdc++ as bytecode, and compiling C++ to C)
Chris Lattner wrote:
> Many aspects of the target compiler can leak through.
So if one wants to use the LLVM system as a cross compiler, one
has to configure llvm-gcc as a cross compiler? Fair enough, I guess.
> One trivial example is:
>
> int X = sizeof(long);
So I assume this also means that while getelementptr insulates
llvm byte code from the details of target specific address
2009 Jun 02
3
[LLVMdev] LLVM frontend supporting arbitrary bit-width integral datatypes
Hello gyus,
I am working on a project, where we are trying to create a development environment
for new ASIP processor design. Part of this project is a compiler generator,
where we would like to generate C compiler from some instruction description.
To keep it short, let's say, that in each instruction's semantics
is described by some C code. What I would like to do is to compile this
2006 Apr 20
2
[LLVMdev] 1.7 Pre-Release Ready for Testing
Hi Pertti,
The boost Python are not (yet) part of LLVM so I suppose it would
make most sense to try to makes fixes/changes so they would work for
1.7 and then try to get them into LLVM CVS. It would be good in such
a case to ask the author of the bindings again if he would allow
this, because basicaly I think he has to agree to the LLVM lincense.
cheers, Eric
On Apr 20, 2006, at 5:08
2007 Nov 27
4
[LLVMdev] LLVM and OpenMP
I am involved in a project where one of the aims is to
study the effects of different parallelization strategies
on efficiency, power consumption etc. The idea is to
do automated design space exploration by varying some
parameters (e.g. number of tasks) and measuring their effect.
Since we are already using LLVM for other purposes, we thought
about using LLVM for analysis and then OpenMP for
2008 Mar 27
1
[LLVMdev] Host leak-through
On Thu, 2008-03-27 at 21:39 +0200, Pertti Kellomäki wrote:
> Except that some aspects of the host platform leak through
> to .bc files. This may or may not be a problem.
A question about this occurred to me last night.
BitC has only one machine-dependent type: word. The current runtime.h
file typedef's this in a machine-dependent way, but all of the C code
emitted by our current back