- User Since
- Nov 20 2018, 10:54 AM (183 w, 3 d)
Wed, May 25
Recommend that you contact NAG for more info on the test suite. Here's the only reference that I could find: https://fortran-lang.discourse.group/t/fortran-compiler-testing-framework/1573/10
This solution looks reasonable for stop messages. I presume it kicks in when running individual tests as well as the suite.
Tue, May 24
My proposal is:
Are you able to use the environment variable NO_STOP_MESSAGE=1 instead?
My belief is that we should wait until f18 hits a reasonable quality bar for executables before making flang-new the default. My reasoning seems not to have carried the day.
Apr 6 2022
I build openmp
Apr 5 2022
Apr 4 2022
As I said this morning, I prefer to wait with this patch until the upstreaming is finished. The reason is not only to do with upstreaming, but also with a concurrent effort to button up any assertion and runtime errors so the initial user experience is better. While some posit the the news of your patch won't be heard around the world, I think it is a major accomplishment & the user community will be thrilled to try flang. My preference is for that first wave of users to come a way with the impression that flang is a high-quality work in progress.
Jan 14 2022
Looks good! Works in my testbed.
Jan 4 2022
Tested and executed. Works for me!
Jan 3 2022
Sep 28 2021
@Meinersbur I understand.
Time to upgrade to C++20?
Sep 1 2021
Aug 8 2021
Jul 27 2021
Looks good! Thanks
Jul 22 2021
Jul 7 2021
Worked for me. Thanks!
May 13 2021
Apr 13 2021
Builds and passed tests for me.
Built & passed tests for me.
Apr 5 2021
Are these warning problems? Is there a reason these aren’t errors? Or have associated file names and line numbers?
Feb 22 2021
Jan 30 2021
Jan 11 2021
Are you able to make a small table for us to look at the whole list of supported fixed and free form sources?
Jan 8 2021
@awarzynski, perhaps I am being too dramatic by wondering if we are compromising support for one or the other language in order to support a common definition. In the case of -I, there are language-specific semantics that are important and interesting, such as the relationship in clang between -I and -isystem, and the relationship in flang between -I and -module. Maybe the right answer is to allow the definition of duplicate options that are differentiated by language?
Jan 6 2021
Flang supports include files and module files. The search path is used to look for both include files and module files. The help text doesn't include info about module files.
I can see how these messages can be useful for a compiler developer; however, perhaps these messages are redundant for end users because other error messages have been issued.
Dec 17 2020
Nov 9 2020
Sep 7 2020
Aug 31 2020
@sameeranjoshi Please consider fixing this issue in the conversion tool (maybe commonmark.py) & propagating the fix to llvm.org?
Aug 27 2020
Aug 25 2020
Aug 22 2020
The install target required me to build all of the documentation. I do not think that is related to this change. Otherwise, the web pages rendered nicely.
Aug 21 2020
Aug 18 2020
Please add a note to the overview about this requirement:
After this patch the markdown docmentation must be written using guide in-
Aug 17 2020
Aug 15 2020
Sorry, I'm not sure what to do next. I'm using cmake vesion 3.18.0 and gcc 9.3.0.
Aug 14 2020
I think you missed one.
Aug 13 2020
Did this work for you?
Aug 12 2020
This worked for me:
I think md is the wave of the future. Other llvm subproject use md. Let's stick with what we have unless there's a compelling advantage to using rst or another format.
Aug 10 2020
This commit has broken the out of tree builds.
Aug 7 2020
Aug 6 2020
Aug 5 2020
out of place as in for a different directive where it is not supported?
The gfortran options is -fimplicit-none. It doesn't appear to have an inverse, but following the convention would be -fno-implicit-none. I think there is value using the same spelling for this option.
Here are the clang definitions:
Do you have a negative test that checks for an out-of-place allocate?
Aug 3 2020
Fix fm324 and fm333. Thanks
Jul 31 2020
No objection to first moving documentation to docs. If someone takes this on, there are links that need to be updated, relatively in the project and in for example Gary's call notes.
Hi Rich, sorry not to have replied to your other review. No one on the NV team needs f18 to read from stdin.
Jul 30 2020
Hi Rich, for clang, for example, what's the process for collecting changes and updating the release notes?
Jul 29 2020
Jul 25 2020
Looks good, Tim. The fcvs tests fm311 passes with this change.
Jul 24 2020
Jul 22 2020
Michael Kruse reports that he has successfully built flang on Windows. Perhaps he could take a look?
Jul 21 2020
Look good. Thanks. P.S. Is someone going to ask about -r8 soon?
Jul 20 2020
The external-hello-world requires input. Does lit handle that well?
Hi David, what is a multi-config generator build? And how do I try it?
Jul 17 2020
The standard goes out of its way not to define blanks.
Jul 15 2020
Hi @jurahul, there's certainly no objection for you to commit this change in llvm-project, especially if the change is required to keep llvm building properly.
Changing the topic a bit:
Jul 14 2020
Tested against a build and install directory; both work great. Thanks.