search for: lingcc

...oked at it, but wasn't able to find where actual instruction bundling takes place, i.e. where exactly in the code they pack instruction into a single bundle. Do you know where it is done? I would really appreciate any pointers. Thanks. On Fri, Sep 25, 2015 at 4:37 PM, Kun Ling <kunling at lingcc.com> wrote: > Hi Rail, > For the VLIW support, Qualcomm's Hexagon target is a good reference. > > http://llvm.org/devmtg/2013-11/slides/Guerra-VLIW.pdf > > > Kun Ling > > > ------------------ Original ------------------ > *From: * "Rail Sha...

...Sincerely > Arvind > > CPU Technology > Software Engineer > > _______________________________________________ > LLVM Developers mailing list > LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu > http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev > -- http://www.lingcc.com

Hi, I have been working towards developing compiler optimization tools targeting multi core processors while using LLVM IR as the starting point and building on top of the analysis and optimization passes available in the llvm source. Recently, I looked into Open64 and its intermediate representation WHIRL. Documentation for developers to use Open64 seems to be inadequate (when compared to LLVM

Is there a VLIW support in LLVM? I found this, https://groups.google.com/forum/#!searchin/llvm-dev/VLIW, but it looks like it is not completely implemented. Specifically I'm interested in how instructions are bundled together. I can't seem to find it anywhere in the source code. Any help in resolving he issue is appreciated. -------------- next part -------------- An HTML attachment was

Hi All, Could anyone point me to some good benchmarking tools to measure the runtime performance of clang compiled C++ applications. Thanks ! - Jyoti -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20131003/3cc029f1/attachment.html>

Hello everyone, Please let me know if you'd like to help providing binaries and testing for your favourite platform. If you were a tester on the previous release, I've bcc'd you on this email. I propose this schedule for the 3.7 release: - 14 July 2015: Create the release branch. - 14 July -- 21 July: Testing Phase I. RC1 binaries are built and tested. - 22 July -- 29 July: Fix

Dear testers, 3.7.0-rc1 was just tagged; please start your testing engines :-) Upload binaries to the sftp and report your results to this thread. I'm sorry for the delay between branching and tagging. The changes to the release script took a little longer than I hoped. Thanks for helping with the release, and do let me know of any issues, questions, etc. The tracking bug for release