[llvm-dev] [RFC] Renaming f18....

Stephen Scalpone via llvm-dev llvm-dev at lists.llvm.org
Thu Jun 6 12:50:59 PDT 2019

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

´╗┐On 4/30/19, 2:02 PM, "llvm-dev on behalf of David Greene via llvm-dev" <llvm-dev-bounces at lists.llvm.org on behalf of llvm-dev at lists.llvm.org> wrote:

    "Finkel, Hal J. via llvm-dev" <llvm-dev at lists.llvm.org> writes:
    > On 4/30/19 9:33 AM, David Greene via llvm-dev wrote:
    >> "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.
    I only suggested a different name because I assumed a different name was
    LLVM Developers mailing list
    llvm-dev at lists.llvm.org

This email message is for the sole use of the intended recipient(s) and may contain
confidential information.  Any unauthorized review, use, disclosure or distribution
is prohibited.  If you are not the intended recipient, please contact the sender by
reply email and destroy all copies of the original message.

More information about the llvm-dev mailing list