search for: pecoff

...Resolver::resolve() /usr2/seaswara/work/llvmorg/llvm-build/../tools/lld/lib/Core/Resolver.cpp:481:7 #10 0x4538f4 lld::Driver::link(lld::LinkingContext&, llvm::raw_ostream&) /usr2/seaswara/work/llvmorg/llvm-build/../tools/lld/lib/Driver/Driver.cpp:108:8 #11 0x425c25 lld::WinLinkDriver::linkPECOFF(int, char const**, llvm::raw_ostream&) /usr2/seaswara/work/llvmorg/llvm-build/../tools/lld/lib/Driver/WinLinkDriver.cpp:879:10 #12 0x42238a lld::UniversalDriver::link(int, char const**, llvm::raw_ostream&) /usr2/seaswara/work/llvmorg/llvm-build/../tools/lld/lib/Driver/UniversalDriver.cp...

...assemblers.  It turns out that MASM syntax is highly ambiguous and MASM is > not production quality for use by a compiler.  This is why visual studio > doesn't go through it.  Long term, we'd like LLVM to be able to write out .o > files directly, if you're interested in adding PECOFF support, that would be > very nice :) Crapola. I was afraid that was going to be the case. This was originally something to do to have fun playing with Objective C, I'm not sure PECOFF support would fall under that :) Any idea how nasty that would be? Oh well, I guess the idea of doing thi...

Hello everyone, I was following the discussion, but I have to admit, that my skills aren't high enough to follow you guys. For my current exception problem, I don't have to stick around with the PECOFF format, so I used clang to don't compile to a PECOFF, but to a ELF file. Interesting, now I'm missing the functions: __cxa_allocate_exception __cxa_throw _ZTI I loaded the DLL "libstdc++.dll" and found all of the addresses - but the application still crashes when the exception...

Hi! I think llvm-mc did amazing work and I'm stunned ;). - So I start reading source-code and making notes. To my question: At which state is the disassembly for PEcoff or ELF? I read the blog (http://blog.llvm.org/2010/04/intro-to-llvm-mc-project.html): """ The MC components have been designed to be object file independent (e.g. work for MachO, ELF, PE-COFF etc) but only have an implementation for MachO (used on Mac OS/X systems). Adding support f...

+ Nick Rui, Does PECOFF writer need the filename in the writer as well, I am not sure if linker scripts are supported with PECOFF though. If PECOFF also needs it, I think it makes sense to store the filename in the Atom as the native format needs to store that information. The only option for the ELF writer to know th...

...hly ambiguous and MASM >>> is >>> not production quality for use by a compiler.  This is why visual studio >>> doesn't go through it.  Long term, we'd like LLVM to be able to write out >>> .o >>> files directly, if you're interested in adding PECOFF support, that would >>> be >>> very nice :) Regarding the pecoff support - FASM comes with complete source and what appears to be a BSD license. It outputs to pecoff. Assuming the FASM code is readable and reasonably understandable, could this code be used as a starting point for...

...s highly ambiguous and >> MASM is >> not production quality for use by a compiler. This is why visual >> studio >> doesn't go through it. Long term, we'd like LLVM to be able to >> write out .o >> files directly, if you're interested in adding PECOFF support, that >> would be >> very nice :) > > Crapola. I was afraid that was going to be the case. This was > originally something to do to have fun playing with Objective C, I'm > not sure PECOFF support would fall under that :) Any idea how nasty > that would be?...

Hi Martell. I too was trying to make the new COFF linker recognize the libraries generated by binutils, but it wasn't resolving the DLLs, just like you described. Apparently it is not identifying the libraries as import libraries but archives. For testing purposes, i've managed to make the old COFF linker work with a simple test case. Had to make two little changes, and link the exe

...<bjoern.gaier at horiba.com> wrote: > > Hello everyone, > > > > I was following the discussion, but I have to admit, that my skills > aren't > > high enough to follow you guys. For my current exception problem, I don't > > have to stick around with the PECOFF format, so I used clang to don't > > compile to a PECOFF, but to a ELF file. Interesting, now I'm missing the > > functions: > > __cxa_allocate_exception > > __cxa_throw > > _ZTI > > > > I loaded the DLL "libstdc++.dll" and found all of th...

Did pecoff support means we can linkage llvm generated obj files to msvc's obj files? 2010/1/22, Jim Crafton <jim.crafton at gmail.com>: >> Nope, llvm's .s output is only compatible with GAS and other at&t syntax >> assemblers.  It turns out that MASM syntax is highly ambiguous...

...dlltool and > the text section comes first rather than last with lib (that probably > doesn't matter much though) > > Please see attached notes.txt with objdump's of both libs > > Can could you give me your thoughts on this and how best we support both > layouts in COFF/PECOFF ? > > What source files should I be looking at to patch this or is this > something you can support with very little effort ? > > I don't know if you would be opposed to supporting this or not being > honest dlltool should generate libs using the same section number as > li...

...t there is no debug section with dlltool and the text section comes first rather than last with lib (that probably doesn't matter much though) Please see attached notes.txt with objdump's of both libs Can could you give me your thoughts on this and how best we support both layouts in COFF/PECOFF ? What source files should I be looking at to patch this or is this something you can support with very little effort ? I don't know if you would be opposed to supporting this or not being honest dlltool should generate libs using the same section number as lib.exe but we can't exactly ch...

...(that probably >>>> doesn't matter much though) >>>> >>>> Please see attached notes.txt with objdump's of both libs >>>> >>>> Can could you give me your thoughts on this and how best we support >>>> both layouts in COFF/PECOFF ? >>>> >>>> What source files should I be looking at to patch this or is this >>>> something you can support with very little effort ? >>>> >>>> I don't know if you would be opposed to supporting this or not being >>>> hone...

...ther than last with lib (that probably >>> doesn't matter much though) >>> >>> Please see attached notes.txt with objdump's of both libs >>> >>> Can could you give me your thoughts on this and how best we support both >>> layouts in COFF/PECOFF ? >>> >>> What source files should I be looking at to patch this or is this >>> something you can support with very little effort ? >>> >>> I don't know if you would be opposed to supporting this or not being >>> honest dlltool should genera...

Hi Martell, Sorry for the belated response. I missed this email. I took a quick look at the library file you have attached and noticed that the file consists of regular object files. LLD expects that all dllimported symbols are described using "short import library" (PE/COFF spec 7). Because I didn't test LLD with dlltool-style archive files, it's no surprise that it didn't

...t section comes first rather than last with lib (that probably >> doesn't matter much though) >> >> Please see attached notes.txt with objdump's of both libs >> >> Can could you give me your thoughts on this and how best we support both >> layouts in COFF/PECOFF ? >> >> What source files should I be looking at to patch this or is this >> something you can support with very little effort ? >> >> I don't know if you would be opposed to supporting this or not being >> honest dlltool should generate libs using the same s...

> By default, the cmake build generates Visual Studio project files for > the X86 target only. Take a look at > > http://www.llvm.org/docs/CMake.html#llvmvars > > for learning how to build other targets. OK thanks, I'll look at that. In the meantime, is it possible to get the assembly generated by llc to work wiht ML? That would probably be the ideal solution. Cheers Jim

...syntax assemblers. It turns out that MASM syntax is highly ambiguous and MASM is not production quality for use by a compiler. This is why visual studio doesn't go through it. Long term, we'd like LLVM to be able to write out .o files directly, if you're interested in adding PECOFF support, that would be very nice :) -Chris

Hi, It looks like each flavor chooses to save references in its own way. The GNU flavor (ELF) uses a single vector of references and uses referenceStartIndex/referenceEndIndex to point to the references for each DefinedAtom. Darwin(Mach-O) / WinLink (PECOFF) uses a different way of storing references ? Is there a plan to make the WinLink/Darwin(Mach-O) use a single vector of references too at some point in time. There are merits/demerits of the approach that the Gnu flavor uses but it would be nice if we settle on one design for storing reference...

Hi Ivan, :) For testing purposes, I've managed to make the old COFF linker work with a > simple test case > Have you got patches for this that I can look at ? Had to make two little changes, and link the exe manually, because the > linker doesn't understand the GNU flags > I've solved the issue of having a GNU driver for the linker so that's not an issue anymore I