similar to: [LLVMdev] Preserve debug information using 'llc -march=c'

Hi all, I'm having an issue with debug information and llc. A test program: #include <iostream> using namespace std; void foo() { cout << "My return address is " << __builtin_return_address(0) << endl << flush; } int main(int argc, char *argv[]) { foo(); return 0; } When I compile my test program to LLVM bytecode, and then use

On Wed, Sep 16, 2009 at 1:34 PM, Nick Jalbert <jalbert at eecs.berkeley.edu> wrote: > Hi all, > I'm having an issue with debug information and llc.  A test program: > #include <iostream> > using namespace std; > void foo() { >     cout << "My return address is " << __builtin_return_address(0) << >         endl << flush; > }

On Mon, 15 Jan 2007, Nick Lewycky wrote: > Eric van Riet Paap wrote: >> *testme.cbe.c:106: error: array type has incomplete element type* > > The problem code boils down to: > > /* Structure forward decls */ > struct l_structtype_s; > > /* Typedefs */ > typedef struct l_structtype_s l_fixarray_array3[3]; > > which is illegal C, but perfectly valid C++,

On 12/10/16 20:32, Matthias Braun via llvm-dev wrote: > But just as food for though: What if msvc did some minimal > optimisations, found out that half the sourcecode is unreachable and > removes it, while llvm with no optimisations just compiles everything? llvm is actually extremely slow when it has to remove lots of dead code. I experienced that in the beginning when working on our

Thanks for the quick responses, but unfortunately still no luck: > llvm-g++ -g -O0 -c -emit-llvm test.cpp > llc -O0 test.o > g++ test.o.s > ./a.out My return address is 0x400bb2 > addr2line 0x400bb2 ??:0 Also to further implicate llc, this works: > llvm-g++ -g -O0 -S test.cpp > g++ test.s > ./a.out My return address is 0x400bf9 > addr2line 0x400bf9

On 2007-01-15, at 11:48, Chris Lattner wrote: > On Mon, 15 Jan 2007, Nick Lewycky wrote: > >> The structure contents are defined right afterwards, but I assume >> that the typedefs are used when emitting the structure contents? >> We may have to put fully defined structures first and typedefs >> second. > > Looks like it. It sounds like the CBE should

To ease portability headaches, I'd like to support several virtual "components" in llvm-config. Possibilities include: all: Include all LLVM libraries. backend: Include either a working native backend or cbackend. engine: Include a working subclass of ExecutionEngine, either the JIT or interpreter. You could, for example, get a typical set of JIT-related libs using:

I'm trying to build driver for hpt374 raid controler on a new installation of contOS 4.2 followin the instroctions in this thread http://www.centos.org/modules/newbb/viewtopic.php?viewmode=flat&order=DESC&topic_id=223&forum=7 It says that I should run "yum install kernel-sourcecode" to get the files I need and it will create the path /usr/src/linux-2.6.9-5.0.3.EL which

Hi, I am using clang::ToolInvocation class to compile some code in-memory: clang::tooling::ToolInvocation ti ( compilerArgs, new clang::EmitBCAction(), new clang::FileManager(clang::FileSystemOptions()) ); //filename is the name of the source file, e.g. "Somefile.cpp" //sourcecode contains the source of the file ti.mapVirtualFile( filename,

Hi, I'm actually afraid that this is a RTFM question - I read the manual but didn't find anything yet... I'm looking for a way to document R sourcecode in my thesis. Does anyone know of a tool or function which can convert or export R sourcecode to Tex? Thanks for any hints! Best Regards, Daniel

RHEL 4 (and thus CentOS 4) do not have appletalk module included. CentOSPlus rather thoughtfully has the 'unsupported' version which would have the appletalk module but I have been unable to get the old megaraid driver to run compiled from the kernel-devel for these 'unsupported' kernels. Thus I would love to simply compile the appletalk module myself from the standard

> I'm sure Oddsock would provide his YP-server-scripts, won't he? > > Otherwise: The calls to the yp-server-scripts should be fairly > simple. Just have a look at the sourcecode ... the yp-server-part > shouldn't be hard to find / "decode". I hope so :) I'm not too good with C or anything like that, so the sourcecode would probably be a bit confusing.

Hi > One would expect this, its a facility of the C++ language. The anonymous > namespace is, essentially, the same as declaring everything in it > static. That is, the symbols are not exported and not available for > linking. Yes, it was pretty clear after finding out that this isn't a linking error which i suspected... > > So for all those trying to add an analysis path:

Hi All, I am trying to recompile the stock kernel to include XFS. At install time of the OS I select to install the kernel source code however I do not have a /usr/src/linux-2.6.9-5.0.3.EL-smp directory. I then learned you must run "yum install kernel-sourcecode" to properly install the source. When I run the command this is what happens ( see below) . The error I get is: warning:

Hi I have just written an pass which does some simple ASAP scheduling. First i registered it as optimization pass because it so nice documented and speeds up the compilation and testing times dramaticly :-). Then i just registered this part as an analysis part which should be used in a modified cbackend. All seems to work fine, exept that llc fails to link. I tried removing the

Hello > What does these mean? The bytecode contains call to intrinsic, which is not supported by by MSIL backend. The only intrinsics currently supported 'natively' are vastart, vaend, vacopy. You might want to extend MSILWriter to use default intrinsic lowering mechanism, however, don't expect, that you'll have something workable - in general, you cannot just grab .c file,

llc -march=x86 tempfileB.bc yields: llc: for the -march option: : Cannot find option named 'x86'! Windows build using Visual Studio 2008 Express with CMake. clang and other tools seem to also complain about the format of -march, but other command line arguments seem to be working. Tools, clang llvm-as, opt, etc., "seem" to be working. Incidently, the bytecode file was

Ok, that makes sense :). , Tobias On Wed, 21 Jul 2004, Chris Lattner wrote: > On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > > void *llvm_gc_read(void *ObjPtr, void **FieldPtr) { > > > return *FieldPtr; > > > } > > > > Hm, but doesn't FieldPtr need to be calculated target-specific in those > > cases? > > For the field pointer, one

I am attempting to recompile the kernel with the following steps. Install kernel-sourcecode rpm cd /usr/src/linux-2.6.9-11.EL cp /boot/config-2.6.9-11.EL .config make menuconfig Device Drivers -> Character Devices -> Serial Drivers change Max number of non legacy 8250_NR_UARTS to 36 make bzImage make modules_install make install Then after rebooting and selecting my -custom

On Wed, 21 Jul 2004, Tobias Nurmiranta wrote: > > Hi, I'm thinking out loud, please give me some feedback. > > Regarding llvm.gcread and llvm.gcwrite, wouldn't it be nicer if they are > implemented as: > > llvm.gcread(sbyte** object, uint offset) > llvm.gcwrite(sbyte* data, sbyte** object, uint offset) > > Where you also have the offset into the object. In