search for: gccint

...gcc-4.2/lib/libstdc++.6.dylib mv %i/share/info/cpp.info %i/share/info/llvm-cpp.info mv %i/share/info/gcc.info %i/share/info/llvm-gcc.info mv %i/share/info/cppinternals.info %i/share/info/llvm-cppinternals.info mv %i/share/info/gccinstall.info %i/share/info/llvm-gccinstall.info mv %i/share/info/gccint.info %i/share/info/llvm-gccint.info mv %i/share/info/libgomp.info %i/share/info/llvm-libgomp.info mv %i/share/info/gfortran.info %i/share/info/llvm-gfortran.info # remove build path from .la files perl -pi -e "s, \-L[^ ']*/%n-%v-%r/llvm_objdir/Release/lib[^ ']*,,g" `find %i/li...

Taking the address of a function inhibits optimisations for that function. Essentially any ABI changes are unavailable if we can't adjust the call site to match. The case of interest here is when a given function is called directly and indirectly, and we don't want the latter to impose a cost on the former. One approach to avoid the ABI constraint cost is to extract/outline the body of an

Hi, DSP-C is an extension to ISO C to support specific hardware features in DSP, e.g. fixed-point typer, memory spaces and circular pointers. It's generic for different DSP's. - http://www.dsp-c.org How difficult is it to extending the llvm-gcc for this extension? Any document like "hitchhiker's guide to extend the GCC fronted" ? (just like the guide for adding

...in compiler development or has relevant out-of-tree work. [0]: https://reviews.llvm.org/D66887 [1]: https://gcc.gnu.org/viewcvs/gcc/trunk/gcc/testsuite/gcc.c-torture/ [2]: https://github.com/llvm/llvm-project/blob/master/llvm/lib/Target/WebAssembly/README.txt [3]: https://gcc.gnu.org/onlinedocs/gccint/C-Tests.html [4]: https://github.com/embecosm/gcc-for-llvm-testing -- Sam Elliott Software Developer - LLVM lowRISC CIC selliott at lowrisc.org --

...en it has some option passed to it. Another would be to enhance > 'collect2' to know about LLVM files. 'collect2' is a GCC utility > invoked at link time, it would be the perfect place to add hooks. I found the documentation of collect2 here: http://gcc.gnu.org/onlinedocs/gccint/Collect2.html Its purpose seems to be to act like ld and insert calls to initialization routines (and exit routines) before calling the real ld. The comment at the top of the source file describes it like this: Collect static initialization info into data structures that can be traversed...

Hello, I recognized that compiler-rt's the implementation of __aeabi_memcpy simply branches to memcpy. The implementation of memcpy is not provided. So an externally provided memcpy () has to be used. (also applies to memmove, memset, memclr) On ARM I have seen implementations of memcpy () using floating-point registers (if compiled with NEON support). The is perfectly legal, as memcpy ()

Hello everybody, During the past week I've kept looking for a solution to this but i couldn't find one, is there really a way to get this type of information or some workaround? Thanks. 2010/12/22 Borja Ferrer <borja.ferav at gmail.com> > Hello, > > Is there a way to determine before register allocation if a virtual reg is > mapped to the lo or hi part of a piece of a

Hello, Is there a way to determine before register allocation if a virtual reg is mapped to the lo or hi part of a piece of a value? Basically i need to tell the register allocator to use a certain set of registers for the lo part and others for the hi part, so in order to do this i would have to know if the data value was expanded into smaller pieces and which piece is each one. Additionally,

Chris, LLVM is an excellent piece of work, LLVM is one of the few project I know that has used the mysterious GCC front-end. I think it will be a great contribution to the community if you could writeup and document how to interface to the GCC front-end data-structures (like LLVM has done). Specifically: a) detail the gcc front-end tree data-structures b) how to go about interfacing to them

On Sep 21, 2007, at 9:42 AM, Maarten ter Huurne wrote: > However, it is not possible to let the zlib Makefile issue that > command > without patching the Makefile, because the fragment that does the > linking is > hardcoded to use the compiler command for linking: > > example$(EXE): example.o $(LIBS) > $(CC) $(CFLAGS) -o $@ example.o $(LDFLAGS) Right,

...passed to it. Another would be to enhance >> 'collect2' to know about LLVM files. 'collect2' is a GCC utility >> invoked at link time, it would be the perfect place to add hooks. > > I found the documentation of collect2 here: > http://gcc.gnu.org/onlinedocs/gccint/Collect2.html > > Its purpose seems to be to act like ld and insert calls to > initialization > routines (and exit routines) before calling the real ld. The > comment at the > top of the source file describes it like this: > > Collect static initialization info into d...

Hi, I'm trying to compile zlib to produce a "libz.a" static library which is an LLVM bytecode archive. I'm using this command line for "configure": AR="llvm-ar r" RANLIB=llvm-ranlib CC=llvm-gcc CFLAGS=--emit-llvm \ ./configure The creation of "libz.a" works, but after that, zlib's Makefile wants to compile and link some example

Le 25/08/2015 20:39, Renato Golin a écrit : > I'm also interested in knowing what you did. I think most people here > would be glad to know your peril and how you solved it. Stack layout: C++ code calls | | JITted C code, compiled and linked on the fly tha calls | | C++ code that throws The throw must pass through the JITted code to arrive at the catch at the top.

...of source basic blocks was replaced by the dispatcher's // basic block it is necessary to update all PHI nodes in source blocks. PHI is a // special artificial definition for supporting the Static Single Assignment form // used for data flow analysis ( http://gcc.gnu.org/onlinedocs/gccint/SSA.html). MovePHINodesToDispatcher( indexBBMap, disMainBB ); return madeChange; } // // Private methods. // unsigned MakeDispatcherPass::IndexSourceBasicBlocks( Function& function, BBindexBBMap& indexBBMap ) { unsigned startIdx = 0; // Keep all source basic blocks, incl...