On Thu, 03 May 2012 18:08:20 -0700 Chris Lattner <[email protected]> wrote:
> > On May 3, 2012, at 1:55 PM, Hal Finkel wrote: > > > Hello, > > > > In order to support our users who have Fortran codes, I would like > > to start working on adding Fortran support into clang. While at > > first this may seem like an odd fit, I think that it should work > > well for two reasons: > > FWIW, I don't think that this makes sense from a community standpoint. > > If you're serious about building a fortran frontend (which would be > really really cool). I think we should start it as another LLVM > subproject. It can certainly build off and use the Clang "liblex" to > get the preprocessor etc, and taking changes to support Fortran into > the clang tree would be perfectly fine. Alright cool, let's do that then. Based on the feedback I've received, it seems like it makes the most sense to add Fortran support directly into the driver and lexer, and keep everything else as a separate subproject. This subproject will have its own Parser, Sema, AST, CodeGen, etc. subdirectories. If we set this up kind of like clang is setup, then the build system will detect whether there is a fortran subdirectory in clang, and if so, will build (defining CLANG_HAS_FORTRAN or something like that) and link the extra components. If we're on the same page, then I'll update my driver/lexer patch to reflect this upcoming configuration. Thanks again, Hal > > -Chris -- Hal Finkel Postdoctoral Appointee Leadership Computing Facility Argonne National Laboratory _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
