#15 closed enhancement (fixed)
parameter_file_flag
Reported by: | Juergen Reuter | Owned by: | kilian |
---|---|---|---|
Priority: | P4 | Milestone: | |
Component: | configure | Version: | 2.0.0alpha |
Severity: | normal | Keywords: | compiler flags |
Cc: |
Description
Add a -O0 flag for compiling the parameter files, since there is nothing to optimize there.
Change History (7)
comment:1 Changed 15 years ago by
Priority: | P3 → P4 |
---|
comment:2 Changed 15 years ago by
Owner: | changed from ALL to kilian |
---|---|
Priority: | P4 → P2 |
comment:3 Changed 15 years ago by
Priority: | P2 → P4 |
---|
comment:4 Changed 15 years ago by
Owner: | changed from kilian to ALL |
---|
comment:5 Changed 15 years ago by
Milestone: | v2-public → v2.0 |
---|---|
Owner: | changed from ALL to kilian |
Status: | new → assigned |
Type: | task → enhancement |
comment:6 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
Done in [1491]. configure now takes an option --enable-optimization-for-parameter-files which is disabled by default.
When disabled, the Make rules for Fortran compilation in the src/models Makefile add -O0 after all compiler flags, including the user flags. This is not good Automake style, but apparently the only possibility that does not violate Automake rules. When enabled, default compilation rules are taken.
Note: See
TracTickets for help on using
tickets.
For the models implemented in r1202 we have the following statistics: using gfortran with -O0 we have real 0m48.765s user 0m41.809s sys 0m5.067s using the compiler defaults (-O2) we have real 2m14.730s user 2m4.247s sys 0m7.029s Unfortunately, the automake/conf construction demands either explicit rules for the compilation of the parameter files or some dirty trick to exclude the standard compiler flags from the path src/models. It's only annoying for developmemnt, not for the user.
We have to discuss what to do here. But I reduce the priority.