Displaying 5 results from an estimated 5 matches for "compmiled".
Did you mean:
compiled
2004 Oct 18
0
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
...9;m not happy with the IncludeFile hack, I can well
> understand why you didn't want to apply it.
One of the funny things about the LLVM Unix build is that we can build
libraries in three different ways: as .a files, as .so files, and as .o
files. The IncludeFile hack is used for libraries compmiled to .a files,
to make 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. T...
2004 Oct 18
3
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
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...
2004 Oct 18
1
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
On Mon, 2004-10-18 at 09:50, Chris Lattner wrote:
> One of the funny things about the LLVM Unix build is that we can build
> libraries in three different ways: as .a files, as .so files, and as .o
> files. The IncludeFile hack is used for libraries compmiled to .a files,
> to make 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 str...
2004 Oct 18
2
[LLVMdev] Fix for non-standard variable length array + Visual C X86 specific code
...rn "C"' in front to know it's
name. It's even worse in my opinion.
> One of the funny things about the LLVM Unix build is that we can build
> libraries in three different ways: as .a files, as .so files, and as .o
> files. The IncludeFile hack is used for libraries compmiled to .a files,
> to make 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 str...
2004 Oct 04
1
[LLVMdev] cfrontend-1.3.source: Compilation error
This is a forward of a question from the SourceForge LLVM forum. If
anyone has experience with Cygwin and building the C front-end there,
please reply and CC Alex.
--- Post by Alex Vinokur below ---
===============
Windows 2000
GNU gcc 3.3.3 (cygwin special)
===============
./configure
./make
I have got compilation error
-------------------------------
make[1]: Entering directory