User Details
- User Since
- Apr 13 2020, 9:02 AM (40 w, 7 h)
Fri, Jan 15
All builds, tests, and looks good.
Thu, Jan 14
All builds, tests, and looks good.
Wed, Jan 13
I changed this update to just add some tests and a new error message.
This is an odd quirk of the language.
Tue, Jan 12
All builds, tests, and looks good.
Fri, Jan 8
Thu, Jan 7
Responding to Jean's comments.
Wed, Jan 6
With Peter's guidance, I changed the definition of actual arguments to allow
for the value of a statement label and changed the code that processes actual
arguments to put the value of the label into the actual argument.
Mon, Jan 4
But how can it be okay for the actual argument to be missing when the corresponding dummy argument is an alternate return?
Dec 18 2020
All builds, tests, and looks good.
All builds, tests, and looks good.
Dec 17 2020
All looks good. I tested the resulting compiler on both in-tree and out-of-tree builds and as able to run "runtest" for all configurations without a problem.
I was able to invoke the "runtest" on both in-tree and out-of-tree builds. What command were you using to invoke "runtest" that caused the problem?
Dec 16 2020
Responses to review comments. I moved the state variable indicating if we're
resolving names in an EQUIVALENCE statement to the class ScopeHandler and used
the existing FindInScope() function to limit name loopups to the current scope
rather than inventing a new interface.
Dec 15 2020
All builds, tests, and looks good.
All builds, tests, and looks good.
All builds, tests, and looks good.
Dec 11 2020
Dec 10 2020
Dec 9 2020
Dec 8 2020
Dec 7 2020
@clementval , never mind. I had a setup error mixing up the "master" and "main" branches.
@clementval , when I build and test an in-tree build, everything works fine. But when I build out-of-tree, the error message associated with line 165 does not appear. Do you know why?
Dec 3 2020
I changed my implementation to just not do semantic checking for EQUIVALENCE
statements when in an interface block.
Dec 2 2020
It would be good to also fix the lint changes that were automatically suggested.
All builds, tests, and looks good.
Nov 18 2020
Nov 17 2020
Aside from the noted items, all builds, tests, and looks good.
Nov 16 2020
I fixed some spelling errors and added a test to verify that the duplicate
ac-implied-do variable names get evaluated correctly in the presence of
constant folding.
Nov 13 2020
Reworked the code to check array shape conformance as suggested by Peter.
Nov 12 2020
All builds, tests, and looks good.
Nov 10 2020
All builds, tests, and looks good.
All builds, tests, and looks good.
Nov 9 2020
Nov 4 2020
Nov 3 2020
All of the flang front end builds without warnings, and everything tests cleanly.
Nov 2 2020
I'm having trouble building and running tests, but all of the changes in this update seem to build and test fine.
Oct 30 2020
All builds, tests, and looks good.
All builds, tests, and looks good.