search for: circt

Sure, I'll summarize with respect to the criterion in the document: - Must be generally aligned with the mission of the LLVM project to advance compilers, languages, tools, runtimes, etc. CIRCT is a compiler which is built around LLVM/MLIR. We anticipate building code generation for ASIC and FPGA backends along with specialized accelerators, while leveraging existing LLVM backends for processor targets. - Must conform to the license, patent, and code of conduct policies laid out i...

For the past several months, members of the ‘CIRCT’ group have been working to begin adapting MLIR for hardware design. We believe that this area would benefit from good open source infrastructure enabling research and, eventually, the next generation of commercial tools. We have collected several dialects and envision a number of lowering flows...

...beat us to the punch as the first external MLIR user :-) but thank you for your support Renato! -Chris > > On Sat, 4 Jul 2020 at 23:30, Stephen Neuendorffer via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> >> >> For the past several months, members of the ‘CIRCT’ group have been working to begin adapting MLIR for hardware design. We believe that this area would benefit from good open source infrastructure enabling research and, eventually, the next generation of commercial tools. We have collected several dialects and envision a number of lowering flows...

...gt; On Wed, 8 Jul 2020 at 22:43, Chris Lattner <clattner at nondot.org> wrote: > > I think that flang beat us to the punch as the first external MLIR user > :-) but thank you for your support Renato! > > Ah, but Flang is in the monorepo and builds together with LLVM, while > CIRCT (and my current project, Verona) "uses" MLIR/LLVM externally (as > a submodule). > > There are a number of build issues in both LLVM and MLIR that make it > awkward for projects in that category to use the LLVM libraries and > having a project in the llvm group will give us...

...attner <clattner at nondot.org> wrote: >>> > I think that flang beat us to the punch as the first external MLIR >>> user :-) but thank you for your support Renato! >>> >>> Ah, but Flang is in the monorepo and builds together with LLVM, while >>> CIRCT (and my current project, Verona) "uses" MLIR/LLVM externally (as >>> a submodule). >>> >>> There are a number of build issues in both LLVM and MLIR that make it >>> awkward for projects in that category to use the LLVM libraries and >>> having...

...different processes: Method 1: start a review with one commit on a new branch (typically in a personal repository 'fork'). Respond to review comments by adding additional commits on the same branch. Then you want to "Squash and Merge". Real life example: https://github.com/llvm/circt/pull/62 Note that Github keeps seems to keep a reference to commits where a review occurred, but does not necessarily preserve other commits in the chain. Also note that you can go back and look at either the final disposition of the code on the main page, or view the diff "as reviewed"...

...; > Method 1: start a review with one commit on a new branch (typically in a > personal repository 'fork'). Respond to review comments by adding > additional commits on the same branch. Then you want to "Squash and > Merge". Real life example: https://github.com/llvm/circt/pull/62 Note > that Github keeps seems to keep a reference to commits where a review > occurred, but does not necessarily preserve other commits in the chain. > Also note that you can go back and look at either the final disposition of > the code on the main page, or view the diff &quo...

On Fri, Sep 11, 2020 at 6:53 PM David Blaikie <dblaikie at gmail.com> wrote: > Is there any observable difference between "Squash and Merge" or "Rebase > and Merge" when "enforce linear history" is enabled, then? > "Squash and Merge" will only generate one commit. > > On Fri, Sep 11, 2020 at 3:45 PM Stephen Neuendorffer via llvm-dev

...review with one commit on a new branch (typically in >>> a personal repository 'fork'). Respond to review comments by adding >>> additional commits on the same branch. Then you want to "Squash and >>> Merge". Real life example: https://github.com/llvm/circt/pull/62 >>> Note that Github keeps seems to keep a reference to commits where a review >>> occurred, but does not necessarily preserve other commits in the chain. >>> Also note that you can go back and look at either the final disposition of >>> the code on the m...

On Tue, 28 Jan 2020 at 12:28, Nicolai Hähnle <nhaehnle at gmail.com> wrote: > I don't quite follow. Yes, gratuitous useless changes tend to create > merge and rebase problems and should generally be avoided. Why does it > make a difference whether they're in multiple commits though? I think you misunderstood. Our policy [1] is that independent NFC fixups on existing code