FYI - I’ve updated the stats to include -O2 in addition to -O3 and -Os:
- https://rv8.io/bench#optimisation
There are 57 plots and 31 tables. It’s quite a bit of data. It will be quite
interesting to run these on new gcc releases to monitor changes.
The Geomean for -O2 is 0.98 of -O3 on x86-64.
On 26/08/2017 17:56, Markus Trippelsdorf wrote:
> On 2017.08.26 at 17:18 +0200, Sylvestre Ledru wrote:
>>
>> On 26/08/2017 13:10, Markus Trippelsdorf wrote:
>>> On 2017.08.26 at 13:04 +0200, Sylvestre Ledru wrote:
Hello,
I have been trying to build the llvm toolchain with gcc 7.2 u
On 2017.08.26 at 17:18 +0200, Sylvestre Ledru wrote:
>
>
> On 26/08/2017 13:10, Markus Trippelsdorf wrote:
> > On 2017.08.26 at 13:04 +0200, Sylvestre Ledru wrote:
> >> Hello,
> >>
> >> I have been trying to build the llvm toolchain with gcc 7.2 using the
> >> Debian packages.
> >> However, it is
On 26/08/2017 13:10, Markus Trippelsdorf wrote:
> On 2017.08.26 at 13:04 +0200, Sylvestre Ledru wrote:
>> Hello,
>>
>> I have been trying to build the llvm toolchain with gcc 7.2 using the
>> Debian packages.
>> However, it is currently failing with some undefined reference.
>> Seems that some sy
On Samstag, 26. August 2017 12:59:06 CEST Markus Trippelsdorf wrote:
> On 2017.08.26 at 12:40 +0200, Allan Sandfeld Jensen wrote:
> > On Samstag, 26. August 2017 10:56:16 CEST Markus Trippelsdorf wrote:
> > > On 2017.08.26 at 01:39 -0700, Andrew Pinski wrote:
> > > > First let me put into some pers
On 2017.08.26 at 13:04 +0200, Sylvestre Ledru wrote:
> Hello,
>
> I have been trying to build the llvm toolchain with gcc 7.2 using the
> Debian packages.
> However, it is currently failing with some undefined reference.
> Seems that some symbols are removed during the build phase (too strong
> op
Hello,
I have been trying to build the llvm toolchain with gcc 7.2 using the
Debian packages.
However, it is currently failing with some undefined reference.
Seems that some symbols are removed during the build phase (too strong
optim?)
I haven't seen something relevant to this in the gcc release
On 2017.08.26 at 12:40 +0200, Allan Sandfeld Jensen wrote:
> On Samstag, 26. August 2017 10:56:16 CEST Markus Trippelsdorf wrote:
> > On 2017.08.26 at 01:39 -0700, Andrew Pinski wrote:
> > > First let me put into some perspective on -Os usage and some history:
> > > 1) -Os is not useful for non-emb
On Samstag, 26. August 2017 10:56:16 CEST Markus Trippelsdorf wrote:
> On 2017.08.26 at 01:39 -0700, Andrew Pinski wrote:
> > First let me put into some perspective on -Os usage and some history:
> > 1) -Os is not useful for non-embedded users
> > 2) the embedded folks really need the smallest code
> On 26 Aug 2017, at 8:39 PM, Andrew Pinski wrote:
>
> On Sat, Aug 26, 2017 at 1:23 AM, Michael Clark wrote:
>> Dear GCC folk,
>> I have to say that’s GCC’s -Os caught me by surprise after several years
>> using Apple GCC and more recently LLVM/Clang in Xcode. Over the last year
>> and a half
> 4) -Os is used heavily by the arm/thumb2 folks in bare metal applications.
Also by the x86 in bare-mental firmware, e.g. http://www.uefi.org/
> For many applications using -flto does reduce code size more than just
> going from -O2 to -Os.
Yes. -flto is must to have, but the -Os is still necess
On 2017.08.26 at 01:39 -0700, Andrew Pinski wrote:
>
> First let me put into some perspective on -Os usage and some history:
> 1) -Os is not useful for non-embedded users
> 2) the embedded folks really need the smallest code possible and
> usually will be willing to afford the performance hit
> 3)
On Sat, Aug 26, 2017 at 1:23 AM, Michael Clark wrote:
> Dear GCC folk,
> I have to say that’s GCC’s -Os caught me by surprise after several years
> using Apple GCC and more recently LLVM/Clang in Xcode. Over the last year and
> a half I have been working on RISC-V development and have been exclu
Dear GCC folk,
I have to say that’s GCC’s -Os caught me by surprise after several years using
Apple GCC and more recently LLVM/Clang in Xcode. Over the last year and a half
I have been working on RISC-V development and have been exclusively using GCC
for RISC-V builds, and initially I was using
14 matches
Mail list logo
