-
Notifications
You must be signed in to change notification settings - Fork 11.3k
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
[Flang] (Semantic check?) Incorrect error message when using the same name in interfaces and external statements #56605
Labels
Comments
@llvm/issue-subscribers-flang-frontend |
@UsmanNadeem Could I get this issue assigned to me? Thanks |
pscoro
added a commit
that referenced
this issue
Feb 7, 2023
…rnal statements and interfaces For issue: #56605. Previous error messages are not descriptive of problem. Issuing warnings instead that do not halt compilation but offer better description of problem. Reviewed By: klausler Differential Revision: https://reviews.llvm.org/D143426
CarlosAlbertoEnciso
pushed a commit
to SNSystems/llvm-debuginfo-analyzer
that referenced
this issue
Feb 8, 2023
…rnal statements and interfaces For issue: llvm/llvm-project#56605. Previous error messages are not descriptive of problem. Issuing warnings instead that do not halt compilation but offer better description of problem. Reviewed By: klausler Differential Revision: https://reviews.llvm.org/D143426
Complete and landed |
veselypeta
pushed a commit
to veselypeta/cherillvm
that referenced
this issue
Aug 9, 2024
…rnal statements and interfaces For issue: llvm/llvm-project#56605. Previous error messages are not descriptive of problem. Issuing warnings instead that do not halt compilation but offer better description of problem. Reviewed By: klausler Differential Revision: https://reviews.llvm.org/D143426
veselypeta
pushed a commit
to veselypeta/cherillvm
that referenced
this issue
Aug 15, 2024
…rnal statements and interfaces For issue: llvm/llvm-project#56605. Previous error messages are not descriptive of problem. Issuing warnings instead that do not halt compilation but offer better description of problem. Reviewed By: klausler Differential Revision: https://reviews.llvm.org/D143426
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The standard states:
I was testing a piece of code (from NumPy) that works fine on Gfortran but did not compile with Flang. I have put a small test case here.
Consider the following two functions where we violate this constraint:
On flang the errors dont make much sense:
Surprisingly, Gfortran is successfully able to compile the second file but we get an appropriate error
Error: Duplicate EXTERNAL attribute specified
for the first file: https://godbolt.org/z/oKq14a9KzWould it be possible to change the error message to something appropriate? Doing so will make debugging much easier.
The text was updated successfully, but these errors were encountered: