[PATCH] D126349: [TableGen] Remove code beads

Sheng via Phabricator via llvm-commits llvm-commits at lists.llvm.org
Fri May 27 21:58:54 PDT 2022


0x59616e added inline comments.


================
Comment at: llvm/utils/gn/secondary/llvm/utils/TableGen/BUILD.gn:15
     "CallingConvEmitter.cpp",
-    "CodeBeadsGen.cpp",
     "CodeEmitterGen.cpp",
----------------
aeubanks wrote:
> myhsu wrote:
> > RKSimon wrote:
> > > 0x59616e wrote:
> > > > myhsu wrote:
> > > > > Thanks for taking care GN as well!
> > > > I did some google, and realize that gn is a build system that can generate ninja build files.
> > > > 
> > > > Why do we have this, given that cmake can do the same thing ?
> > > Its used by some teams - the agreement was that it could be in the repo as long as everyone else doesn't have to worry about it :) Often you'll see auto? updates to the gn files after the equivalent cmakelists.txt file has been updated.
> > > I did some google, and realize that gn is a build system that can generate ninja build files.
> > > 
> > > Why do we have this, given that cmake can do the same thing ?
> > 
> > GN has some advantages over cmake in terms of generating Ninja. For instance, the reconfiguration speed after a GN file modification is much faster than that of a cmake file modification. But as Simon mentioned, currently in LLVM it's just an optional Ninja generation method for some teams to use for easier integration with their existing build environment.
> GN is an unsupported build system for LLVM, no need to update it if you aren't actively using it. better to let the bot update these files anyway if you aren't going to test it
Thanks for explanation ;) 

As aeubanks suggested, I'll revert it in the next diff.


Repository:
  rG LLVM Github Monorepo

CHANGES SINCE LAST ACTION
  https://reviews.llvm.org/D126349/new/

https://reviews.llvm.org/D126349



More information about the llvm-commits mailing list