Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Look into changing gnu optimization setting to -O0 on izumi #198

Open
cacraigucar opened this issue Dec 17, 2024 · 1 comment
Open

Look into changing gnu optimization setting to -O0 on izumi #198

cacraigucar opened this issue Dec 17, 2024 · 1 comment

Comments

@cacraigucar
Copy link

On izumi, when using code compiled with the current -Og setting, a good number of variables are "optimized out" when viewing in totalview. Changing this setting in two places in the cmake_macros/gnu.cmake file before running case.build yields variables which are able to be viewed in the totalview debugger.

There was some discussion on investigating the timing impact of making this change on CESM regression tests.

If the timing is not significantly impacted, I would like to suggest that gnu use the -O0 setting for debug cases.

@fischer-ncar
Copy link
Collaborator

I just did some quick build tests on izumi using QPC6. -O0 builds look to be faster than -Og.

-Og builds
Total build time: 330.851402 seconds
Total build time: 345.887056 seconds

-O0 builds
Total build time: 284.907677 seconds
Total build time: 275.838053 seconds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants