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

Misleading "Literal too large for compiler" error #47

Open
dmikushin opened this issue Nov 21, 2023 · 3 comments
Open

Misleading "Literal too large for compiler" error #47

dmikushin opened this issue Nov 21, 2023 · 3 comments

Comments

@dmikushin
Copy link

I get "Literal too large for compiler" error from the following contexts:

Error:./mma114.f:79,22:
   Literal too large for compiler
      ZDC( IDX4+J ) = (0.0,0.0)
                      ^
Error:./mma403.f:91,29:
   Literal too large for compiler
      IF ( ZC( INDXBV ) .EQ. 0.0D0 ) GO TO 1450
                             ^

Do you have an idea what this error means?

@ben-brewer-codethink
Copy link
Member

So the code which handles this is here:

ofc_sparse_ref_error(typeval->src,

The intention is that it reports when you have an integer that's over 64-bit (8 bytes) or a floating point type that's bigger than a long double (10 bytes) as these are not currently supported.

@ben-brewer-codethink
Copy link
Member

Would it be possible to get a minimal test which triggers this issue?

@dmikushin
Copy link
Author

Hi @ben-brewer-codethink , I apologize that I won't be able to really minimize the test cases. But as you said the problem should be straight-forward. I'm attaching the original source file mentioned above, FYI it's a part of NASTRAN-95 distribution:

mma114.f.gz

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