Displaying 3 results from an estimated 3 matches for "1110173ar66".
2011 Nov 14
2
[LLVMdev] Performance Tracking
...they look pretty good. Aside from things that use OpenMP or benefit from autovectorisation, Clang/LLVM and GCC seem to come fairly close, with no overall winner.
But: there do seem to have been a number of performance regressions between 2.9 and 3.0:
http://openbenchmarking.org/result/1110178-AR-1110173AR66
Identifying where these were introduced is quite difficult. I wonder if some of the buildbots could be persuaded, after building clang, to build and run some benchmark projects (e.g. perlbench, povray, flac / lame, whatever) and email people if they introduce a performance regression, just as the...
2011 Nov 14
0
[LLVMdev] Performance Tracking
...hings that use OpenMP or benefit from autovectorisation, Clang/LLVM and GCC seem to come fairly close, with no overall winner.
Nice. Thanks.
>
> But: there do seem to have been a number of performance regressions between 2.9 and 3.0:
>
> http://openbenchmarking.org/result/1110178-AR-1110173AR66
>
> Identifying where these were introduced is quite difficult. I wonder if some of the buildbots could be persuaded, after building clang, to build and run some benchmark projects (e.g. perlbench, povray, flac / lame, whatever) and email people if they introduce a performance regression, j...
2011 Nov 16
2
[LLVMdev] [cfe-dev] Performance Tracking
...ovectorisation, Clang/LLVM and GCC seem to come fairly close, with no
> overall winner.
>
> Nice. Thanks.
>
> >
> > But: there do seem to have been a number of performance regressions
> between 2.9 and 3.0:
> >
> > http://openbenchmarking.org/result/1110178-AR-1110173AR66
> >
> > Identifying where these were introduced is quite difficult. I wonder if
> some of the buildbots could be persuaded, after building clang, to build
> and run some benchmark projects (e.g. perlbench, povray, flac / lame,
> whatever) and email people if they introduce a p...