Ticket #93 (closed enhancement: invalid)

Opened 11 years ago

Last modified 11 years ago

xuvtools: (xuvbuild.sh) add possibility to set compiler optimizations

Reported by: ne704 [niko@… Owned by: ne704
Priority: minor Milestone:
Component: xuvtools Version:
Keywords: xuvtools, buildsystem Cc: niko@…, mario@…

Description

the buildscript should be able to set compiler optimizations on windows, which consists of two parts:

  • define the sub-project(s) where the settings apply
  • define the optimization settings

Change History

Changed 11 years ago by ne704

  • status changed from new to assigned

Changed 11 years ago by ne704 [niko@…

tried with the following settings:

Configuration: Release

Configuration Properties
    \_ C/C++
       \_ Code Generation
          \_ Enable Enhanced Instruction Set = /arch:SSE3
          \_ Add Processor-Optimized Code Path = /QaxSSSE3 (note the difference between QaxSSE3 and QaxSSSE3!)
          \_ Intel Processor-Specific Optimization = /QxSSSE3

Changed 11 years ago by ne704 [niko@…

  • cc mario@… added

I recently tried several settings (win64) with our test-dataset "To15100740xm", the intel-compiler ICC 11.1.038 // 11.1.051 and "no optimizations" vs. "/arch:SSE3 /QaxSSSE3 /QxSSSE3", it didn't make any noticable difference.

So, do we really need the optimization stuff? At least with ICC I suppose the don't have to be set explicitly. To figure out if we need them for example for the VS-compiler, we should define a test-sequence for measuring performance.

Just for documentation, Mario's suggestions for older ICC-versions were: at least SSE2 on processor-specific stuff, and as many as possible on processor-optimized stuff (if I remember right, this used to be /QaxWPTS on older ICC).

Changed 11 years ago by ne704 [niko@…

Shall we close this bug?

Changed 11 years ago by ne704 [niko@…

  • status changed from assigned to closed
  • resolution set to invalid

Closing this bug as invalid. Feel free to reopen if unhappy.

Note: See TracTickets for help on using tickets.