- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
ifort 2022 (linux WSL) cannot compile the following code snippet.
Is the compiler error correct? Is line continuation disallowed in this case?
integer, allocatable :: A(:)
A = [integer &
:: 0]
end
1 Solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Considering the Fortran standard document,
- Re: "Is the compiler error correct?" - no. Intel Fortran does not conform by failing to process the continued statement.
- Re: "Is line continuation disallowed in this case?" - no. Per the standard, the shown continuation is allowed.
Link Copied
7 Replies
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Considering the Fortran standard document,
- Re: "Is the compiler error correct?" - no. Intel Fortran does not conform by failing to process the continued statement.
- Re: "Is line continuation disallowed in this case?" - no. Per the standard, the shown continuation is allowed.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
A temporary workaround until a compiler resolution might be to move the double colon separator to the previous line:
integer, allocatable :: A(:)
A = [ integer :: &
& 0 ]
end
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Uh, oh! This one almost slipped by!
Thanks for reporting it. I filed the bug as CMPLRLLVM-43404.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Fantastic. Thank you for your meticulous attention to bug reports and surely not the least, for the great compilers.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We have a fix in the pipeline for this bug. The fix will appear in the 2024.2.0 ( Update 2). This is roughly due end of June or in July 2024.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
fantastic! Thank you.
Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page