search for: dissassembl

...g executed. I also insured that it was getting called > before the module was written out, and that no additional debug information > gets added after it has been called. > > Yet despite this, the second-to-last parameter for DW_TAG_subprogram > metadata is in fact null in the module dissassembly. > > So essentially I am completely stumped. > > > If you're using DIBuilder to create your subprogram then you'll see that it > puts new node in AllSubprograms. > > // Create a named metadata so that we do not lose this mdnode. > > > AllSubprograms.pus...

...Builder::finalize(). But even with that change I am getting an error when I try to run llc: Assertion failed: (TheCU && "Unable to find compile unit!"), function endFunction, file /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. And looking at the .bc dissassembly, I see there are indeed compile unit MDNodes, although at this level I can't tell if they are hooked up correctly. On Wed, Aug 31, 2011 at 9:07 AM, Devang Patel <dpatel at apple.com> wrote: > > On Aug 22, 2011, at 6:48 AM, Irina Lipov wrote: > > Hi, > I saw your update r...

...code was being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called. > > Yet despite this, the second-to-last parameter for DW_TAG_subprogram metadata is in fact null in the module dissassembly. > > So essentially I am completely stumped. If you're using DIBuilder to create your subprogram then you'll see that it puts new node in AllSubprograms. // Create a named metadata so that we do not lose this mdnode....

...e that the code was being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called. Yet despite this, the second-to-last parameter for DW_TAG_subprogram metadata is in fact null in the module dissassembly. So essentially I am completely stumped. On Mon, Sep 26, 2011 at 8:01 AM, James Molloy <James.Molloy at arm.com> wrote: > Hi Talin, > > Followup as promised: in our case we weren't calling finalize(). As this > manifests itself as exactly the same assertion failure as your...

...error when I try to run llc: > > > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > > endFunction, file > > /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line > 1306. > > > > And looking at the .bc dissassembly, I see there are indeed compile unit > > MDNodes, although at this level I can't tell if they are hooked up > correctly. > > you might want to take a look at this llvm-gcc commit: > > r137753 | dpatel | 2011-08-16 23:03:26 +0200 (Tue, 16 Aug 2011) | 3 lines > > DIBui...

...s being executed. I also insured that it was getting called before the module was written out, and that no additional debug information gets added after it has been called. >> >> Yet despite this, the second-to-last parameter for DW_TAG_subprogram metadata is in fact null in the module dissassembly. >> >> So essentially I am completely stumped. > > If you're using DIBuilder to create your subprogram then you'll see that it puts new node in AllSubprograms. > > // Create a named metadata so that we do not lose this mdnode....

...n with that change I am getting an error when I try to run llc: > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > endFunction, file > /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. > > And looking at the .bc dissassembly, I see there are indeed compile unit > MDNodes, although at this level I can't tell if they are hooked up correctly. you might want to take a look at this llvm-gcc commit: r137753 | dpatel | 2011-08-16 23:03:26 +0200 (Tue, 16 Aug 2011) | 3 lines DIBuilder is moving forward to reduce in m...

...ert, Thanks for the info, you've confirmed what I was trying to do, but when I compile: ----------------------- #include <stdio.h> int main(int argc, char *argv[]) { printf("yo\n"); return 0; } ----------------------- without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not call __main: ----------------------- ; ModuleID = '<stdin>' target endian = little target pointersize = 32 target triple = "i686-pc-linux-gnu" deplibs = [ "c", "crtend" ] %struct..TorRec = type { int, void ()* } %struct.TorRe...

...pu=vfp -g -lm -o all-types_gcc Compiler options used for clang were as follows: /usr/local/bin/clang all-types.c -w -ccc-gcc-name arm-linux-gnueabi-gcc -ccc-host-triple arm-linux-gnueabi -ccc-clang-archs arm -march=armv7-a -mtune=cortex-a8 -mfloat-abi=softfp -mfpu=vfp -g -lm -o all-types Dissassembly of main() from all-types.c compiled with GCC. 00008448 <main>: float v_float; double v_double; int main () { 8448: e92d4800 push {fp, lr} 844c: e28db004 add fp, sp, #4 extern void dummy(); #ifdef use...

...Address-exposed local */ ... *(&ltmp_3355_85) = ltmp_75_3; *(&ltmp_3356_105) = ltmp_76_9; initLogging((&ltmp_3355_85), (&ltmp_3356_105), 1, 0); ----- The C code is what I intended. That leaves me to believe that my transformation produced the correct bytecode, but the dissassembler is not properly disassebling the bytecode. Ryan Ryan M. Lefever wrote: > I am writing a transformation that needs to add a call to a function F() > at the beginning of main() with the addresses of argc and argv as > parameters to F(). However, the bytecode file I'm transformin...

...lc: > > > > Assertion failed: (TheCU && "Unable to find compile unit!"), function > > endFunction, file > > /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. > > > > And looking at the .bc dissassembly, I see there are indeed compile unit > > MDNodes, although at this level I can't tell if they are hooked up correctly. > > you might want to take a look at this llvm-gcc commit: > > r137753 | dpatel | 2011-08-16 23:03:26 +0200 (Tue, 16 Aug 2011) | 3 lines > &g...

...y to run llc: >>> >>> Assertion failed: (TheCU && "Unable to find compile unit!"), function >>> endFunction, file >>> /Users/talin/Projects/llvm/lib/CodeGen/AsmPrinter/DwarfDebug.cpp, line 1306. >>> >>> And looking at the .bc dissassembly, I see there are indeed compile unit >>> MDNodes, although at this level I can't tell if they are hooked up correctly. >> >> you might want to take a look at this llvm-gcc commit: >> >> r137753 | dpatel | 2011-08-16 23:03:26 +0200 (Tue, 16 Aug 2011) | 3...

Hi Folks , The problems with HPlip goes on and on : I can not manage to establish a connection on WiFi with the HP4620 : I can print to the printer but not scan . Running hp-check results in cups is not running, hplip is not properly (HP) installed , xsane is not installed etc.. But I can assure you all this software is properly installed : Hp-check cannot detect the scanfunction on

...> support: >> Arrogance or stupidity ? >> > The inheritance of Carly. I was on the phone yesterday to HP - we just > bought this $$$$ printer, and it's under warranty. The engineer I spoke > with told me he'd been there since '99, and he could tell me how to > dissassemble and rebuild this brand new poster printer in his sleep. He > does not, however, know software.... When I mentioned that HP has support > in '12 for Macs - I was hoping to get the .ppd from the Mac package, as we > had for the z3200ps in '12 - he told me they'd gotten rid of th...

...> > In case of Dell XPS 9560 (IIRC that's the machine you have) the > > corresponding power resource is called \_SB.PCI0.PEG0.PG00 and its > > _ON/_OFF methods end up calling PGON()/PGOF() accordingly. The methods > > itself do lots of things and it is hard to follow the dissassembled > > ASL which does not have any comments but there are couple of things that > > stand out where we may go into a different path. One of them is this in > > the PGOF() method: > > > > If (((OSYS <= 0x07D9) || ((OSYS == 0x07DF) && (_REV == 0x05)))) >...

I am writing a transformation that needs to add a call to a function F() at the beginning of main() with the addresses of argc and argv as parameters to F(). However, the bytecode file I'm transforming has not allocated space on the stack for argc and argv. So, I developed my transformation to change main() from: ----- int main(int %argc, sbyte** %argv){ entry: ... // some use of

On Aug 22, 2011, at 6:48 AM, Irina Lipov wrote: > Hi, > I saw your update regarding "The DIBuilder interface used by front ends to encode debugging information in the LLVM IR now expects clients to use DIBuilder::finalize() at the end of translation unit to complete debugging information encoding" > Does it mean that in the new version you defer emission of some debug info

...all other users do not need > support: > Arrogance or stupidity ? > The inheritance of Carly. I was on the phone yesterday to HP - we just bought this $$$$ printer, and it's under warranty. The engineer I spoke with told me he'd been there since '99, and he could tell me how to dissassemble and rebuild this brand new poster printer in his sleep. He does not, however, know software.... When I mentioned that HP has support in '12 for Macs - I was hoping to get the .ppd from the Mac package, as we had for the z3200ps in '12 - he told me they'd gotten rid of the Mac support t...

The -c option tells llvm-gcc to build a bytecode file without linking in the LLVM runtime library. This is similar to the -c option for regular gcc, which you use to build multiple separate .o files that you're going to link into a single executable. If you want to build from a single source file, it's easiest just to compile without the -c option. If you're building from

On Sun, Feb 26, 2006 at 10:00:18PM -0800, Wink Saville wrote: > Thanks for the info, you've confirmed what I was trying to do, but when > I compile: [snip] > without "-c" (llvm-gcc t1.c -o t1) the dissassembled bytecode does not > call __main: __main() is used to run static constructors and destructors, so if you're compiling without -c, LLVM knows all the files you're compiling and if there are no static constructors, __main() is not necessary (or if it's there, it's empty, and can...