> On Aug 9, 2016, at 10:46 AM, Erik Eckstein via swift-evolution
> wrote:
>
>>
>> On Aug 9, 2016, at 10:19 AM, Wallacy via swift-evolution
>> > wrote:
>>
>> I believe the -O is already able to loop
I believe the -O is already able to loop unroll, but now C-Style loop is
gone, and maybe will be more "difficult" to compiler make this
optimization, except of course using range literals.
Em ter, 9 de ago de 2016 às 13:10, Muse M via swift-evolution <
swift-evolution@swift.org> escreveu:
>
-Oloop
Correction: it should be similar to GCC -funroll-loops
On other option if we have 1,000,000's loops or array, it's bad for one
core to handle 100% of the calculations and other cores are idle, the idea
could be optimize loops to share/split workload across all available CPU
cores.
My understanding is that -Ounchecked removes integer overflow checks and array
bound checks.
What type of optimizations would -Oloop and -Ofunction do?
Félix
> Le 7 août 2016 à 19:27:56, Muse M via swift-evolution
> a écrit :
>
> I'm not sure if this is the right
I'm not sure if this is the right channel to discuss on optimization switch
We are aware the 3 options:
-O
-Ofast
-Ounchecked
As we can see, we rarely use -Ounchecked for safety reason and there aren't
much info on what are the tradeoff. if there are performance reason that
will need to improve