search for: libx86

...e sure that the library is actually linked in. The other two types of library (X86 is a .o file version) do not have this problem: they "library" either gets linked in as a unit or not. I'm not sure if VC has something like this, but I strongly suspect it does. The trick is getting libx86 to compile as a single unit that is forced to link in. -Chris -- http://llvm.org/ http://nondot.org/sabre/

Chris Lattner wrote: > Can you explain what goes wrong without the stub? It's the only part that > I didn't apply. The X86 backend doesn't get registered since there are no references to symbols in X86TargetMachine the object file is never pulled in from the library I create, and thus the static intializer for the RegisterTarget is never called...

...s actually linked in. The other two types > of library (X86 is a .o file version) do not have this problem: they > "library" either gets linked in as a unit or not. > > I'm not sure if VC has something like this, but I strongly suspect it > does. The trick is getting libx86 to compile as a single unit that is > forced to link in. It depends on whether the linker can "relink" a set of object files into another object file instead of an executable. Morten, what you want to set up is the ability to do something like: link a.obj b.obj c.obj /out abc.obj (...

I downloaded Wine sources with Git. Now when I cd to wine-git folder and do ./configure, at the end I get a message: Code: "configure: WARNING: No OpenGL library found on this system. OpenGL and Direct3D won't be supported. configure: Finished. Do 'make depend && make' to compile Wine." I installed all packages from this script - http://kegel.com/wine/hardy.sh

...by Sean, and #4 is basically a heavily refactored version of asmprinter:printInstruction (which I'm working on). A strong goal for me is to make it so that we can build very small (as in code size) assembler and disassembler tools. This means that none of this stuff can depend on (e.g.) libx86, because that brings in the huge target plus libcodegen plus libtarget plus vmcore, ... etc. As a key part of this factoring, instruction asmprinting (for example) will no longer work directly on MachineInstr. Instead, asmprinter::printInstruction will lower a MachineInstr to an MCInst,...

...psys2-dev | libcupsys-dev libgif-dev | libungif4-dev libjack0.100.0-dev libaudio-dev lib32asound2-dev libssl-dev libcapi20-dev docbook-utils docbook-xsl docbook-to-man libjpeg62-dev libxslt1-dev libxxf86vm-dev prelink libsane-dev libhal-dev libhal-storage-dev libc6-dev-i386 lib32z1-dev gcc-multilib libx86-dev dpkg-buildpackage: warning: Build dependencies/conflicts unsatisfied; aborting. dpkg-buildpackage: warning: (Use -d flag to override.) Build command 'cd wine-1.1.4~winehq0~ubuntu~8.04 && dpkg-buildpackage -b -uc' failed. E: Child process failed I noticed the "unmet build d...

Can someone explain what MCInst is vs. MachineIntr? I'm porting some patches we have here that affect MachineInstrs and am wondering whether I need to make similar changes in MCInst. Why do we have two machine instruction representations? -Dave

...s actually linked in. The other two types > of library (X86 is a .o file version) do not have this problem: they > "library" either gets linked in as a unit or not. > > I'm not sure if VC has something like this, but I strongly suspect it > does. The trick is getting libx86 to compile as a single unit that is > forced to link in. maybe it's possible to put many objects together into one with the visual studio compiler also, but I don't really know how to do it... especially not if you want to stick with the normal .sln/.vcproj build system... m.

Hi, I''m trying to port AMD VGA passthru patch to the latest XEN and vanila kernel and I got SIGSEGV in static void ati_hw_out(uint16_t hport, uint32_t data) { ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 1); asm volatile ("out %1, %0"::"Nd"(hport),"a"(data)); ioperm(gfx_info.host_pio_base, gfx_info.pio_size, 0); } I tried old 2.6.32

...ng the parsing logic that maps from "opcode name + argument" in the asmparser to an instruction enum value + MCOperands. 4. Refactor the asm printer to go through MCStreamer instead of writing to raw_ostream directly (in progress). 5. Refactor the asm printer to not depend at all on libx86, codegen, vmcore etc. The goal is for x86/asmprinter to only depend (at a link level) on libsupport. There is a lot involved in this, to say the least, but this is important for "llvm-mc as a disassembler API". 6. Implement the "assembler middle end", which handles relax...