On terça-feira, 3 de maio de 2016 19:27:03 PDT maitai wrote:
> Interesting... Besides Android, is it worth considering -O3 for
> Linux/OS-X/Windows for a heavy-calculation application ?
YMMV, so benchmark and come up with your conclusions.
You may want to turn on vectorisation reports from your c
Thiago,
Thanks for your explanation.
I will try to understand if it is bringing me benefits or not.
Regards,
Nuno
> On 03 May 2016, at 18:18, Thiago Macieira wrote:
>
> On terça-feira, 3 de maio de 2016 18:14:11 PDT Nuno Santos wrote:
>> Because, from my experience with the code compiled f
Interesting... Besides Android, is it worth considering -O3 for
Linux/OS-X/Windows for a heavy-calculation application ?
Philippe Lelong
Le 03-05-2016 19:18, Thiago Macieira a écrit :
On terça-feira, 3 de maio de 2016 18:14:11 PDT Nuno Santos wrote:
Because, from my experience with the code co
03.05.2016, 20:14, "Nuno Santos" :
> Because, from my experience with the code compiled for Intel, putting -O3
> made a huge difference on the processing code of my audio app. But the same
> might not be valid for arm. That’s why I’m asking.
Note that embedded CPUs usually have small caches, s
On terça-feira, 3 de maio de 2016 18:14:11 PDT Nuno Santos wrote:
> Because, from my experience with the code compiled for Intel, putting -O3
> made a huge difference on the processing code of my audio app. But the same
> might not be valid for arm. That’s why I’m asking.
-O3 not only enables all
Because, from my experience with the code compiled for Intel, putting -O3 made
a huge difference on the processing code of my audio app. But the same might
not be valid for arm. That’s why I’m asking.
I’m trying to squeeze the most of the C++ code performance on Android.
> On 03 May 2016, at 1
>From https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html
-Os
Optimize for size. -Os enables all -O2 optimizations that do not typically
increase code size. It also performs further optimizations designed to
reduce code size.
-Os disables the following optimization flags:
-falign-f
Em terça-feira, 3 de maio de 2016, às 18:00:07 PDT, Nuno Santos escreveu:
> I mean -O2, like the others
You didn't answer why you think that it's important to use -O2 instead of -Os.
The reason why it's using -Os instead of -O2 was probably because the
maintainers of the Android port thought tha
I mean -O2, like the others
Nuno Santos
Founder / CEO / CTO
www.imaginando.pt
+351 91 621 69 62
> On 03 May 2016, at 06:27, Thiago Macieira wrote:
>
> On segunda-feira, 2 de maio de 2016 22:07:03 PDT Nuno Santos wrote:
>> Hi,
>>
>> Below are the CFLAGS for Android
>> (Qt/5.6/android_armv7/mksp
On segunda-feira, 2 de maio de 2016 22:07:03 PDT Nuno Santos wrote:
> Hi,
>
> Below are the CFLAGS for Android
> (Qt/5.6/android_armv7/mkspecs/android-g++/qmake.conf)
>
> I’m wondering why there are no optimisation settings for arm rather than
> size. Is there any specific reason?
Why should the
Hi,
Below are the CFLAGS for Android
(Qt/5.6/android_armv7/mkspecs/android-g++/qmake.conf)
I’m wondering why there are no optimisation settings for arm rather than size.
Is there any specific reason?
QMAKE_CFLAGS_WARN_ON= -Wall -Wno-psabi -W
QMAKE_CFLAGS_WARN_OFF = -Wno-psabi
equals(AND
11 matches
Mail list logo
