similar to: [LLVMdev] libSystem, __clear_cache(), FreeBSD and ARM

Hi all, When you genetate code on PowerPC you need to explicitly invalidate the instruction cache to force the processor to reread it. In LLVM there is code to do this for function stubs on Macintosh, but not for other platforms and not for JITted code generally. The attached patch adds support for GNU platforms, but I can't figure out a nice way to call it for all generated code. Can

Hi,   The link and the information shared was helpful.   I will make my problem definition more clear. While I am "asm printing" target code, I also want to emit scope related information. Scope related information includes, - for each scope, start line, end line, start column, end column and - scope heirarchy. As scope is delimited by "{" and "}" (for an input

Pankaj, If you want to decorate MachineInstrs then for the end of scope you're not looking at "}" but instead you're looking at _last_ machine instruction in that scope. Now, if you want to find out start and end MachineInstrs for a lexical scope (and corresponding line numbers) then see CodeGen/LexicalScopes pass. It collects lexical scope information and maps MIs to respective

I am about to write general functions to read the output of simulations models. These model generate output files with different sections which I want to analyze plot etc. Since this will be used many people at the department I wanted to make sure that will do this in the best way. For instance I want to read a snippets of data from a text that look like this.

Pankaj, On Oct 3, 2011, at 4:36 AM, Pankaj Gode wrote: > Hi All, > > int global; > int func( int t) > { > //scope 1 > { > .... > } <----- > return x; > } > > For the above code, i want to collect endline (indicated by <---) for the scope. Can we get this information from the Dwarf Information in llvm 2.9 ? > If there is no code

Hi All,   int global; int func( int t) {    //scope 1   {      ....   } <-----   return x; }   For the above code, i want to collect endline (indicated by <---) for the scope. Can we get this information from the Dwarf Information in llvm 2.9 ?     Thanks & Regards, Pankaj -------------- next part -------------- An HTML attachment was scrubbed... URL:

On Mon, 16 Jun 2008, Gary Benson wrote: > When you genetate code on PowerPC you need to explicitly invalidate > the instruction cache to force the processor to reread it. In LLVM > there is code to do this for function stubs on Macintosh, but not > for other platforms and not for JITted code generally. Applied, thanks!

Seeing the below commit, I wondered whether that's a genuine fix or rather a workaround for a shortcoming in llvm::ScopedPrinter::printNumber. The latter has overloads for [u]int{8,16,32,64}_t, presumably so that it can take arguments of arbitrary integer types. However, at least on recent macOS uint64_t is 'unsigned long long' (and uint32_t is 'unsigned int') while

projects/compiler-rt/lib/builtins/clear_cache.c I suggest two small changes here. 1. Mark it however required to avoid inlining, i.e. for the x86/amd64 case. Control transfer is required. I realize it is likely anyway, you aren't likely to "fall from" the caller into the code. 2. #elif defined(_WIN32) && (defined(__arm__) || defined(__aarch64__)) be changed to just: #elif

Chris Lattner wrote: > On Mon, 16 Jun 2008, Gary Benson wrote: > > When you genetate code on PowerPC you need to explicitly > > invalidate the instruction cache to force the processor to reread > > it. In LLVM there is code to do this for function stubs on > > Macintosh, but not for other platforms and not for JITted code > > generally. > > Applied, thanks!

I've noticed that when you debug a function that was loaded into the workspace using the source function, it prints the location of the file from which the function was sourced. Is there a way to get that same information without debugging the function? Thanks, Scott

Hi all I received the following patch for compiling ctypes module for Python on FreeBSD from Keith White (I'm in no position to judge this fix, I'm just passing it on). Is there anyone on this list being able to commit this code? Thxs, Werner =================================================================== --- contrib/compiler-rt/lib/clear_cache.c (revision 250739) +++

Hello, I've just found that the current SVN trunk has some toolchain dependencies on ARM cross compiling. i.g. the __clear_cache in lib/System/Memory.cpp is not defined in my toolchain (codesourcery 2007q3, gcc version 4.2.1). What is the official(?) toolchain version used for ARM cross-compilation? Best, Hyok -------------- next part -------------- An HTML attachment was

crossposted to wine-dev, and wine-users Hi, I've done some more tests, and i found that when i run winedbg starcraft and wine starcraft and then again winedbg starcraft etc. It works, but always following this pattern: <boot my box> winedbg starcraft :all runs perfectly wine starcraft: all video choppy winedbg starcraft :all runs perfectly winedbg starcraft: all video choppy wine

Hello Community :) I've a problem with Steam/Counter Strike Source and Wine, I've installed Steam (with no errors) with wine version: wine 1.1.44-1 and downloaded Counter Strike Source. If I tried to start it, it failed so I read something about ingame community should be disabled, I did and I added the -dxlevel 70 option to my "startline", it works! I also can join games and

Prasanth J wrote: > Hi, > > I can able to compile LLVM using armgcc_4.3.3 (codesourcery2009q1..).. > but when i tried to run it on target it shows GCC 4.3.0 version not > found. So i copied the runtime libraries (libc.so and libgcc_s.so) > from the toolchain to the target and exported its path in > LD_LIBRARY_PATH. But when i tried to run any llvm tools on target its >

Prasanth J skrev: > Hi, > > i am a newbie to llvm architecture. i have been trying to port llvm on > ARM target. i am using the following configuration for cross compiling > llvm. > > ../llvm/configure --host=arm-linux --target=arm-linux > --build=i686-linux --prefix=/opt/llvm-arm/ --enable-optimized > --disable-debug \ > --disable-expensive-checks --disable-doxygen

Hi, I can able to compile LLVM using armgcc_4.3.3 (codesourcery2009q1..).. but when i tried to run it on target it shows GCC 4.3.0 version not found. So i copied the runtime libraries (libc.so and libgcc_s.so) from the toolchain to the target and exported its path in LD_LIBRARY_PATH. But when i tried to run any llvm tools on target its crashing with Segmentation fault. What could be the problem

http://bugs.freedesktop.org/show_bug.cgi?id=20780 Summary: nouveau corrupts and crashes on 7800gt when NoAccel=false after a few drawing operations Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium

Prasanth J wrote: > Hi, > > As you said i downloaded arm toolchain from codesourcery(2009q3 with > gcc 4.4.1 version).. if i use this toolchain i am getting the > following error.. > > make[2]: Entering directory > `/home/prasanth/LLVM_ARM/llvm-with-armgcc441/llvm-obj/lib/Analysis' > llvm[2]: Compiling LoopPass.cpp for Release build > if arm-none-linux-gnueabi-g++