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

Compiler dependent crashes #16

Open
acmnpv opened this issue Oct 12, 2015 · 2 comments
Open

Compiler dependent crashes #16

acmnpv opened this issue Oct 12, 2015 · 2 comments
Assignees
Labels

Comments

@acmnpv
Copy link
Contributor

acmnpv commented Oct 12, 2015

Qdyn5p, version 5.06 crashed when using the Intel Fortran compiler at version 15.. while optimizations (-O3) are turned on. The crash happens in the torsion subroutine code near the entry point and is not found for either version 12.1.4 or 14.0.2 of the compiler, or when optimizations are disabled with -O0.

If other compiler dependent crashes are found, please add them to this issue

@acmnpv acmnpv added the bug label Oct 12, 2015
@acmnpv acmnpv self-assigned this Oct 12, 2015
@esguerra
Copy link
Member

In which test does it crash?
Does it crash for compilations coming from the current master branch?
I remember that discussion we had about optimal compiler options now, perhaps we should have it again?

Perhaps looking into the Release notes might help:

https://software.intel.com/en-us/articles/optimization-notice#opt-en
https://software.intel.com/en-us/articles/intel-composer-release-notes-by-version

Is it processor specific (read the optimization notice)?

@acmnpv
Copy link
Contributor Author

acmnpv commented Oct 14, 2015

Hello,
the crash occurred for a basic system provided by Martin Floor (see recent message on the mailing list) under the 15.0.0 version and the 15.0.0.90 version
It crashes only if the -O3 flag was set, no crash happened for -O0.
The crash was just after entry into the torsion function, but no further cause could be found because of the optimization.
With the new master branch version, no crash happens. This is scary because it means there is a hidden bug somewhere in the code

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

No branches or pull requests

2 participants