Hi Eric,
On Sun, Sep 8, 2013 at 7:00 PM, Eric van Riet Paap wrote:
> What is the PyPy speed difference after using gcc versus llvm for the
> compilation of the PyPy-c backend?
Currently, it seems that using the LLVM IR static translation backend
of PyPy gives higher performance. We're still tr
On Sun, Sep 8, 2013 at 11:17 AM, Armin Rigo wrote:
> Hi again,
>
> On Sun, Sep 8, 2013 at 9:42 AM, Armin Rigo wrote:
>> We've been suitably impressed by the results on the new llvm backend
>> during the sprint (well, or suitably un-impressed by both gcc and
>> clang's failure to reconstruct the S
On Sun, Sep 8, 2013 at 5:42 PM, Armin Rigo wrote:
> Hi Alex,
>
> On Sun, Sep 8, 2013 at 5:33 PM, Alex Gaynor wrote:
>> LLVM also has a link time optimization, is it on by default in LLVM, or do
>> we need to benchmark with it enabled explicitly?
>
> The point I made in my mail was that the llvm b
Hi,
I am missing some background information to follow what is being discussed
here, so...
What is the PyPy speed difference after using gcc versus llvm for the
compilation of the PyPy-c backend?
Would generating .ll instead of .c files really give any benefit?
More interesting would still be
Hi Alex,
On Sun, Sep 8, 2013 at 5:33 PM, Alex Gaynor wrote:
> LLVM also has a link time optimization, is it on by default in LLVM, or do
> we need to benchmark with it enabled explicitly?
The point I made in my mail was that the llvm backend is written in a
way that makes link-time optimizations
LLVM also has a link time optimization, is it on by default in LLVM, or do
we need to benchmark with it enabled explicitly?
Alex
On Sun, Sep 8, 2013 at 8:17 AM, Armin Rigo wrote:
> Hi again,
>
> On Sun, Sep 8, 2013 at 9:42 AM, Armin Rigo wrote:
> > We've been suitably impressed by the results
Hi again,
On Sun, Sep 8, 2013 at 9:42 AM, Armin Rigo wrote:
> We've been suitably impressed by the results on the new llvm backend
> during the sprint (well, or suitably un-impressed by both gcc and
> clang's failure to reconstruct the SSA meaning of the C code).
I have investigated a bit more a
Hi Manuel,
We've been suitably impressed by the results on the new llvm backend
during the sprint (well, or suitably un-impressed by both gcc and
clang's failure to reconstruct the SSA meaning of the C code).
The current issue seems to be debugging. It would be nice if gdb
presented at least sou
