search for: ppcg

I got your point. Thank you, and I'd like to provide the relative message now. But firstly, what do you mean by the "relevant command generated by your makefile"? What I can tell you now is: The Error Message: make[3]: Entering directory `/home/tang.kk/ppcg/ppcg/isl/interface' CXXLD extract_interface extract_interface.o:(.data.rel.ro._ZTI13MyASTConsumer[typeinfo for MyASTConsumer]+0x10): undefined reference to `typeinfo for clang::ASTConsumer' collect2: ld returned 1 exit status make[3]: *** [extract_interface] Error 1 make[3]: Leaving dire...

Jun-qi Deng <dengjunqi06323011 at gmail.com> writes: >> Is it? In my experience, it isn't. Please show the relevant command >> generated by your makefile and the associated error message(s). >> > >> RTTI is an on/off option that changes per LLVM library, so setting >> -fno-rtti for using LLVM makes no sense. VMCore and Support have -frtti >> while

> > Recently I think I found a bug in llvm's CMakeLists.(I use llvm 3.1svn > and > > Clang 3.1) I follow the normal way to try to compile an application that > > utilize both clang and llvm: I ./autogen.sh it, ./configure it and make > it. > > But the make fails. At last I found out the failure is because that the > > Makefile's CXXFLAGS does not contain

...I am saying directly to convert C code to PTX assembly. On Tue, Dec 11, 2018 at 12:19 PM Madhur Amilkanthwar <madhur13490 at gmail.com> wrote: > You can skip CUDA code generation and target PTX assembly. PTX is a common > assembly language for NVIDIA's GPU. You may want to look at PPCG, Pluto > projects to get a hint of how automatic CUDA code can be generated by > compilers. They are based on polyhedral model so come with some inherent > limitations. > > On Tue, Dec 11, 2018, 12:07 PM hameeza ahmed via llvm-dev < > llvm-dev at lists.llvm.org wrote: > >...

...: > I got your point. Thank you, and I'd like to provide the relative message > now. But firstly, what do you mean by the "relevant command generated by > your makefile"? What I can tell you now is: > > The Error Message: > make[3]: Entering directory `/home/tang.kk/ppcg/ppcg/isl/interface' > CXXLD extract_interface > extract_interface.o:(.data.rel.ro._ZTI13MyASTConsumer[typeinfo for > MyASTConsumer]+0x10): undefined reference to `typeinfo for > clang::ASTConsumer' > collect2: ld returned 1 exit status [snip] So you define a class MyAstC...

Hello, I need to ask, like automatic compiler vectorization, can GPU ISA be generated automatically, by skipping the CUDA programming? For instance if i just write C code there can be 2 possibilities, semi and full automatic. In case of semi, we can write #pragma directives to say this should be run on gpu. hence can the compiler generates directly gpu ISA, skipping CUDA code? In case of fully

...> !11 = distinct !DICompileUnit(language: DW_LANG_C89, file: !3, producer: > > "julia", isOptimized: true, runtimeVersion: 0,emissionKind: FullDebug, > > enums: !12) > > > > This was generated by verifyModule(*GPUModule,&(llvm::errs())From whithin > > PPCGCodeGeneration.cpp in Polly. > > > > From <llvm_src>/test/Verifier/dbg-orphaned-compileunit.ll, I understand > > that the debug info, of a compile unit, represented by !11 is missing from > > llvm.dbg.cu. > > > > What does this mean ? What could have caused...

...ical, and can be simplified to not make explicit usage of transitive closure computations. There is much research to be done in the area, with short term applications and implementation in production. E.g., on-demand expansion on top of the Live Range Reordering technique implemented in isl and PPCG (papers and slides below): http://impact.gforge.inria.fr/impact2016 > [2] - https://hal.archives-ouvertes.fr/hal-01257316/document That one is rather specific to parallel programs and also theoretical. State of the art: - POPL 2016 http://conf.researchr.org/event/POPL-2016/popl-2016-papers-sm...

2016-06-27 15:52 GMT+05:00 4lbert C0hen <4lbert.h.c0hen at gmail.com>: > Dear Roman and all, > > Such features would be extremely useful to implement array expansion (scalar > and array renaming, privatization with new subscript expressions of higher > dimension) and storage mapping optimization (generalizing array > contraction). It would be interesting to have these

Hello, Le 12/12/2016 à 18:29, Hans Wennborg a écrit : > +Sylvestre who knows about these things. > > On Thu, Dec 8, 2016 at 2:24 AM, Kris van Rens via llvm-dev > <llvm-dev at lists.llvm.org> wrote: >> L.S., >> >> I'm currently in the process of creating Debian packages for >> clang/llvm release 3.9.0. For this I'm using the steps as explained on

...er.dir 836K build/lib/Target/AMDGPU/InstPrinter/CMakeFiles/LLVMAMDGPUAsmPrinter.dir 824K build/lib/ToolDrivers/llvm-dlltool 808K build/lib/ToolDrivers/llvm-dlltool/CMakeFiles 804K build/lib/ToolDrivers/llvm-dlltool/CMakeFiles/LLVMDlltoolDriver.dir 800K build/tools/polly/lib/External/CMakeFiles/PollyPPCG.dir 796K build/tools/polly/lib/External/CMakeFiles/PollyPPCG.dir/ppcg 768K build/tools/clang/test/CXX/modules-ts 764K build/tools/clang/test/Modules/Output/dependency-dump-dependent-module.m.tmp 752K build/unittests/Support 752K build/lib/Target/PowerPC/Disassembler 744K build/tools/clang/unittests...