search for: cppbackend

...vm" > output? If you mean the former, then would that be easy for someone who > hasn't seen the clang source before? > Generally the latter - then potentially set some breakpoints & look at the clang source if you're looking for the right APIs. It's not as easy as the CppBackend (if the CppBackend were up to date) but not too bad, I don't think. > > On Wed, May 4, 2016, 22:48 David Blaikie <dblaikie at gmail.com> wrote: > >> The usual advice I provide people is "see what Clang does with an >> equivalent C construct" >> >&...

Hello, I was trying to compile a simple program with the CppBackend like so: $ clang str_arg.c -emit-llvm -S $ llc -march=cpp str_arg.ll It produces a file `str_arg.cpp` as expected, however it doesn't seem that the resulting file is correct. For once, it includes `<llvm/Analysis/Verifier.h>` which seems to have been moved to `llvm/IR/Verifier.h` as far...

The usual advice I provide people is "see what Clang does with an equivalent C construct" On Wed, May 4, 2016 at 12:18 PM, Stanislav Manilov < stanislav.manilov at gmail.com> wrote: > Hi, > > There is another benefit to keeping the CppBackend: it's great for > learning how to use the IR and the C++ API in particular, as can be seen > from this SO Q&A: > http://stackoverflow.com/questions/16656855/llvm-ir-string-initialization > > But I'll understand if it's considered too much of a burden to keep. I can &g...

Hi, I was trying to do a source to source transformation in llvm from c++11 more basic c++ (to transform away auto etc.) using llvm3.1. I generate llvm bitcode using "clang++ -emit-llvm ...", but executing llc -march=cpp throws /home/broes/software/llvm/lib/Target/CppBackend/CPPBackend.cpp:493: void {anonymous}::CppWriter::printAttributes(const llvm::AttrListPtr&, const string&): Assertion `attrs == 0 && "Unhandled attribute!"' failed. Does this point to some unimplented feature of the transformation? thanks in advance, Broes -----------...

...tion -cppfor=main -o - This command is supposed to generate the C++ code to construct the main function in LLVM (see main_llvm2cpp.cc joined file). But an error occurs while generating the code (see stack trace below). It appears that an assertion is broken while treating attributes in the file CPPBackend.cpp. So I dumped the main function's attributes before treating them, here is the result: PAL[ { ~0U => *nounwind uwtable* "less-precise-fpmad"="false" "no-frame-pointer-elim"="false" "no-frame-pointer-elim-non-leaf"="true" &...

...ered instead of many people crafting some half-working > > ashamed kludges far from the sight... :-) > Not really. There's no reason to spend the effort just because "in the > future someone might use it". > If you're saying "I have some half-working things and CppBackend would > be awesome for me", then I guess no one would object to you working on > it, and people would actually help if you needed advice/patch review, > etc. > > But if we have no one actively interested, and there has been no > active development to the point where it's...

>>>>> On Tue, 3 May 2016 16:36:01 -0400, Rafael Espíndola via llvm-dev <llvm-dev at lists.llvm.org> said: Rafael> Care to send a patch deleting it? :-) On the other hand these requests come back from time to time on the mailing list and it is still used in many attics of various projects as a de-facto internal representation to interface with other tools for

...te: > > AFAICT it is dead. > > On Tue, May 3, 2016 at 4:04 AM, Stanislav Manilov via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > Hello, > > I was trying to compile a simple program with the CppBackend > like so: > > $ clang str_arg.c -emit-llvm -S > $ llc -march=cpp str_arg.ll > > It produces a file `str_arg.cpp` as expected, however it > doesn't seem that the resulting file is correct. For once, it > includes `<llvm/...

...at lists.llvm.org> wrote: > >> AFAICT it is dead. >> >> On Tue, May 3, 2016 at 4:04 AM, Stanislav Manilov via llvm-dev < >> llvm-dev at lists.llvm.org> wrote: >> >>> Hello, >>> >>> I was trying to compile a simple program with the CppBackend like so: >>> >>> $ clang str_arg.c -emit-llvm -S >>> $ llc -march=cpp str_arg.ll >>> >>> It produces a file `str_arg.cpp` as expected, however it doesn't seem >>> that the resulting file is correct. For once, it includes >>> `<ll...

Is there example code of how to construct the CPPTargetMachine and run addPassesToEmitFile method with Kaleidoscope example? Any help is appreciated. Thanks. Richard Catlin -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130401/cd082202/attachment.html>

> * Has there ever been an attempt to implement a real C++ Backend? Without > having done research in that direction - shouldn't that be quite > straightforward? Anyone aware of technical difficulties? The first question probably is what it would be useful for? -- With best regards, Anton Korobeynikov Department of Statistical Modelling, Saint Petersburg State University

On 23 May 2016 at 15:01, James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> wrote: > There was, a long time ago, a backend that actually targetted C. It was > deleted in 2012 at r153307. It was largely unmaintained, and its tests were failing all the time when we targeted other architectures. I think it'd be cool to have a back-end targeting C/C++, but it'd have to be

...an Silva via llvm-dev < llvm-dev at lists.llvm.org> wrote: > AFAICT it is dead. > > On Tue, May 3, 2016 at 4:04 AM, Stanislav Manilov via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> Hello, >> >> I was trying to compile a simple program with the CppBackend like so: >> >> $ clang str_arg.c -emit-llvm -S >> $ llc -march=cpp str_arg.ll >> >> It produces a file `str_arg.cpp` as expected, however it doesn't seem >> that the resulting file is correct. For once, it includes >> `<llvm/Analysis/Verifier.h>`...

...; This command is supposed to generate the C++ code to construct the main > function in LLVM (see main_llvm2cpp.cc joined file). > But an error occurs while generating the code (see stack trace below). > > It appears that an assertion is broken while treating attributes in the file > CPPBackend.cpp. > So I dumped the main function's attributes before treating them, here is the > result: > > PAL[ > { ~0U => nounwind uwtable "less-precise-fpmad"="false" > "no-frame-pointer-elim"="false" "no-frame-pointer-elim-non-leaf&q...

...(ch >= '0' && ch <= '9') || ch == '_')) { char buffer[5]; - sprintf(buffer, "_%x_", ch); + snprintf(buffer, sizeof(buffer), "_%x_", ch); VarName += buffer; } else VarName += ch; Index: lib/Target/CppBackend/CPPBackend.cpp =================================================================== --- lib/Target/CppBackend/CPPBackend.cpp (revision 117247) +++ lib/Target/CppBackend/CPPBackend.cpp (working copy) @@ -224,7 +224,7 @@ Out << "APFloat("; #if HAVE_PRINTF_A char Buffer[100]; -...

...lib/` is a bug. > > $ git grep -l 'outs()' -- lib/ > lib/ExecutionEngine/Interpreter/ExternalFunctions.cpp > lib/IR/GCOV.cpp > lib/Support/CommandLine.cpp > lib/Support/FormattedStream.cpp > lib/Support/TargetRegistry.cpp > lib/Support/raw_ostream.cpp > lib/Target/CppBackend/CPPBackend.cpp > > All of these cases seem to be for outputting help text of some sort. But > probably they should be passed a reference to a `raw_ostream`, so that the > caller gets to choose whether or not to use `outs()`. > > Were you hitting one of these? > _______________...

...--git a/lib/Target/LLVMBuild.txt b/lib/Target/LLVMBuild.txt index 4112046..6e42cbe 100644 --- a/lib/Target/LLVMBuild.txt +++ b/lib/Target/LLVMBuild.txt @@ -16,7 +16,7 @@ ;===------------------------------------------------------------------------===; [common] -subdirectories = ARM AArch64 BPF CppBackend Hexagon MSP430 NVPTX Mips PowerPC R600 Sparc SystemZ X86 XCore +subdirectories = ARM AArch64 BPF CppBackend Hexagon MSP430 NVPTX Mips PowerPC R600 Sparc SystemZ X86 XCore Foo ; This is a special group whose required libraries are extended (by llvm-build) ; with the best execution engine (the n...

I was just fixing a bug that was caused by `stdout` being closed before the runtime has done `fflush(stdout)` [or however this is implemented in the runtime]. The cause of this seems to be that `outs()` returns a static object created from `raw_fd_stream(STDOUT_FILENO, true)` - the `true` being the `shouldClose` parameter. Surely LLVM is not supposed to close `stdout` as part of its operations?

...112046..6e42cbe 100644 >> --- a/lib/Target/LLVMBuild.txt >> +++ b/lib/Target/LLVMBuild.txt >> @@ -16,7 +16,7 @@ >> >> ;===------------------------------------------------------------------------===; >> >> [common] >> -subdirectories = ARM AArch64 BPF CppBackend Hexagon MSP430 NVPTX Mips >> PowerPC R600 Sparc SystemZ X86 XCore >> +subdirectories = ARM AArch64 BPF CppBackend Hexagon MSP430 NVPTX Mips >> PowerPC R600 Sparc SystemZ X86 XCore Foo >> >> ; This is a special group whose required libraries are extended (by >> l...

...BUILD_TYPE=MinSizeRel > -DCMAKE_CXX_COMPILER=/usr/local/bin/clang++ > -DCMAKE_C_COMPILER=/usr/local/bin/clang -DCMAKE_CXX_FLAGS='-O2' > CMAKE_C_FLAGS='-O2' -DLLVM_BUILD_EXAMPLES=ON -DLLVM_BUILD_TESTS=ON > -DLLVM_INCLUDE_TESTS=ON > -DLLVM_TARGETS_TO_BUILD='ARM;CppBackend;PTX;Hexagon;X86' ../trunk/llvm/ > -- Target triple: x86_64-unknown-linux-gnu > -- Native target architecture is X86 > -- Threads enabled. > -- Building with -fPIC > -- Constructing LLVMBuild project information > -- Targeting ARM > -- Targeting CppBackend > -- Targeting...