Skip to content

Make real128 optional #83

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

Closed
wants to merge 2 commits into from
Closed

Conversation

scivision
Copy link
Member

this same concept is readily extended to other types. Based on the current architecture, this seemed to be the most expedient way to make a kind optional.

The only thing lacking is the Makefiles--how would you prefer to handle having some files .F90 and some .f90. One way would be to just make all the files .F90 as there is no harm in preprocessing every file, and eventually all the files may have preprocessing anyway.

@certik
Copy link
Member

certik commented Jan 5, 2020 via email

@scivision
Copy link
Member Author

Both PGI and Flang are broken in multiple ways for Fortran 2003. It might be best to just wait for them to fix themselves. However if there's any other non-universal kind we wish to add, it would currently be done perhaps like this, unless we refactored. E.g. if someone wants real16 or something.

So while this PR may be unnecessary as is, something like this would need to be done to accomodate kinds not available in all systems. Or a refactor.

@scivision
Copy link
Member Author

So this PR fixes only part of the things wrong with Flang and PGI. The rest are due to improper implementation of Fortran 2003 in Flang/PGI.

@scivision scivision closed this Jan 6, 2020
@scivision scivision mentioned this pull request Jan 6, 2020
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

Successfully merging this pull request may close these issues.

2 participants