search for: libbcc

...localhost ~]# /usr/share/bcc/tools/opensnoop Traceback (most recent call last): File "/usr/share/bcc/tools/opensnoop", line 19, in <module> from bcc import ArgString, BPF File "/usr/lib/python3.6/site-packages/bcc/__init__.py", line 27, in <module> from .libbcc import lib, bcc_symbol, bcc_symbol_option, _SYM_CB_TYPE File "/usr/lib/python3.6/site-packages/bcc/libbcc.py", line 17, in <module> lib = ct.CDLL("libbcc.so.0", use_errno=True) File "/usr/lib64/python3.6/ctypes/__init__.py", line 343, in __init__ self...

This is getting a bit off-topic, but since Renato brought up RenderScript, I wonder if the Android libbcc interface wouldn't be a cleaner way to approach this problem. It provides more or less the same functionality as MCJIT and in almost the same way. -Andy From: llvmdev-bounces at cs.uiuc.edu [mailto:llvmdev-bounces at cs.uiuc.edu] On Behalf Of Renato Golin Sent: Tuesday, November 05, 2013 12:...

Hi mailing list, I has been working on a large project that is based on LLVM 3.1. Recently we are thinking to introduce an LLVM bc converter from LLVM 3.9 to LLVM 3.1, such that we can introduce some of the newest LLVM analyses and optimizations to our LLVM 3.1 based project. Have you worked on similar things that converting LLVM bc downward and has anything to share? Thanks Hongbin

Thanks Steve and Mehdi for the explanation. Steve, I am a little be confused by looking at the code in https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/BitReader_3_0/BitcodeReader.cpp. Looks like the BitcodeReader do some translation while reading the bitcode. If LLVM ToT can read the bitcode of LLVM 3.0, while can't we just use the bitcode reader in LLVM ToT? Also, the bitcode "downgrade" is done by : // Use the LLV...

...;> kubakuderski+llvm at gmail.com> wrote: >>> >>>> Hi Hongbin, >>>> >>>> Android's RenderScript uses a tool like that. You can find the sources >>>> here: >>>> https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/ >>>> . >>>> >>>> Best, >>>> Jakub >>>> >>>> >>>> On 2 August 2016 at 11:10, Hongbin Zheng via llvm-dev < >>>> llvm-dev at lists.llvm.org> wrote: >>>> >>>>&...

...>>>>> >>>>>> Hi Hongbin, >>>>>> >>>>>> Android's RenderScript uses a tool like that. You can find the >>>>>> sources here: >>>>>> https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/ >>>>>> . >>>>>> >>>>>> Best, >>>>>> Jakub >>>>>> >>>>>> >>>>>> On 2 August 2016 at 11:10, Hongbin Zheng via llvm-dev < >>>>>> llvm-dev...

...ug 2, 2016 at 3:06 PM, Jakub Kuderski <kubakuderski+llvm at gmail.com <mailto:kubakuderski+llvm at gmail.com>> wrote: > Hi Hongbin, > > Android's RenderScript uses a tool like that. You can find the sources here: https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/ <https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/> . > > Best, > Jakub > > > On 2 August 2016 at 11:10, Hongbin Zheng via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: >...

...t 3:06 PM, Jakub Kuderski <kubakuderski+llvm at gmail.com <mailto:kubakuderski+llvm at gmail.com>> wrote: >> Hi Hongbin, >> >> Android's RenderScript uses a tool like that. You can find the sources here: https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/ <https://android.googlesource.com/platform/frameworks/compile/libbcc/+/master/bcinfo/> . >> >> Best, >> Jakub >> >> >> On 2 August 2016 at 11:10, Hongbin Zheng via llvm-dev <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm...

On 4 November 2013 23:45, James Lyon <jameslyon0 at gmail.com> wrote: > I'm trying to build LLVM on Android rather than the other way around! > Really just to see if it can be done. I worked out the first problem (my > code was written for the old JIT and I'd missed something in updating to > the MCJIT to make it work on ARM). It still doesn't work, but at this

I'm trying to build LLVM on Android rather than the other way around! Really just to see if it can be done. I worked out the first problem (my code was written for the old JIT and I'd missed something in updating to the MCJIT to make it work on ARM). It still doesn't work, but at this point I have no idea why and it'll be a while before I get to look at it again: the Android