search for: d30897

Displaying 3 results from an estimated 3 matches for "d30897".

Did you mean: 30897
2017 Mar 17
2
Sharing MemoryBuffers between front ends and LLVM
...errer Ibanez via llvm-dev <llvm-dev at lists.llvm.org> wrote: >> >> Hi all, >> >> I'm implementing interleaved source in assembly output. Early reviews raised the concern > Is there a patch up for review? https://reviews.llvm.org/D30898 https://reviews.llvm.org/D30897 > I’m wondering how is the frontend enabling this interleaved output mode? I'm not sure this has been really discussed in the review yet (although there certainly is a proposed mechanism in the patches). -Hal > > — > Mehdi > > >> that the current implementation wi...
2017 Feb 03
3
RFC: Add a way to interleave source code in assembler output
Dear llvm/clang community, I'm interested in adding a way to emit source code interleaved in the output of the assembler. - Introduction A feature that several compilers have and clang/llvm is missing is the possibility of interleaving source code in the assembler output (e.g. when using -S). This feature is useful for a number of reasons. For those users who are concerned with the quality
2017 Mar 16
4
Sharing MemoryBuffers between front ends and LLVM
Hi all, I'm implementing interleaved source in assembly output. Early reviews raised the concern that the current implementation will be opening files (using a llvm::MemoryBuffer) that are likely to be in the memory of the front end (commonly clang but I think we want this to be front end agnostic). I'm now exploring ideas to avoid reopening files and let LLVM reuse the files the FE had