[RFC] Renaming f18....

We’d like to recommend “fortran” as the name of the source repository, mailing list (fortran-dev), and the C++ namespace. The source code is all about Fortran so people working on the compiler and tools will be thinking fortran first and foremost.

As for the driver, time will tell. I expect the f18 developers at Arm will post an RFC asking for advice about how to write the driver. Base it on clang or start fresh? Extract the clang driver into its own project? Name it flang? But that’s another RFC.

Thanks in advance for your feedback,

  • Steve

"fortran" seems far too generic to me. What distinguishes it from a
different Fortran compiler?

What about "flange" (Fortran language environment)? It's distinct from
the already-in-use-by-two-projects "flang" yet fits in with the existing
"clang" naming scheme. Plus it captures the fact that the Fortran
runtime is a rather large piece of work.

                          -David

Stephen Scalpone via llvm-dev <llvm-dev@lists.llvm.org> writes:

Yeah, I agree. What's wrong with flang? My guess is that you're trying to avoid confusion with the older flang project, but I think that's impossible. :slight_smile: You could call it anything and you're still going to get messages on the new list asking about the old thing, people replying saying that it's the wrong list, etc. But eventually the older one will go away and "flang-dev@lists.llvm.org" won't be ambiguous anymore.

-Troy

"fortran" seems far too generic to me. What distinguishes it from a
different Fortran compiler?

What about "flange" (Fortran language environment)? It's distinct from
the already-in-use-by-two-projects "flang" yet fits in with the existing
"clang" naming scheme. Plus it captures the fact that the Fortran
runtime is a rather large piece of work.

I think that we should call the project flang and the name of the drive
should also be flang. With all due respect to the other projects called
flang, and I've been involved in at least two of them, the goal has
always been to have an upstream fortran compiler called flang, and if
this is our upstream fortran compiler, it should be called flang.

The fact that the Clang mailing list is called cfe-dev, etc. instead of
clang-dev, etc. is confusing to those outside of the community. I think
that we should not repeat that kind of difference, and we should name
the mailing lists, directories, etc. based on "flang" as well.

Thanks again,

Hal

"Finkel, Hal J. via llvm-dev" <llvm-dev@lists.llvm.org> writes:

My opinion should be weighted weakly here, but I am also +1 on “flang”. I completely agree with Hal that the cfg-dev vs clang-dev naming thing was a mistake, and hopefully the cfe repo will get renamed to clang as well with the GitHub move.

-Chris

So "flang" it is. I'll ask the llvm-admin team to create a flang-dev mailing list and the required repos and directories for tools/flang. Thanks everyone for your feedback.

- Steve

    "Finkel, Hal J. via llvm-dev" <llvm-dev@lists.llvm.org> writes:

Great news! Thanks!