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

Validate that GNU compile options produce numerically-safe binaries #53

Open
kvrigor opened this issue Jan 24, 2025 · 0 comments
Open
Labels
build-issue Build errors and other compiler-related issues.

Comments

@kvrigor
Copy link
Member

kvrigor commented Jan 24, 2025

Related to #52 . The current set of GNU compiler flags needs to be scrutinized if they actually produce numerically-safe code.

if(COMPILER STREQUAL "GNU")
add_compile_definitions(CPRGNU)
set(CMAKE_C_FLAGS "-std=gnu99 -fopenmp")
set(CMAKE_C_FLAGS_DEBUG "-fcheck=bounds")
set(CMAKE_C_FLAGS_RELEASE "-O")
set(CMAKE_Fortran_FLAGS "-fconvert=big-endian -ffree-line-length-none -ffixed-line-length-none -ffree-form -fopenmp -fallow-argument-mismatch")
set(CMAKE_Fortran_FLAGS_DEBUG "-g -Wall -Og -fbacktrace -ffpe-trap=zero,overflow -fcheck=bounds")
set(CMAKE_Fortran_FLAGS_RELEASE "-O")

@kvrigor kvrigor changed the title Validate that GNU compile options produce numerically binaries Validate that GNU compile options produce numerically-safe binaries Jan 24, 2025
@kvrigor kvrigor added the build-issue Build errors and other compiler-related issues. label Jan 24, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build-issue Build errors and other compiler-related issues.
Projects
None yet
Development

No branches or pull requests

1 participant