similar to: [LLVMdev] Win32 COFF Support

On Sun, Sep 26, 2010 at 3:28 PM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords > <blunted2night at gmail.com> wrote: > > Hi guys, > > While trying to get dwarf debugging information to work with Win32 COFF > > targets, I came across a couple of issues with the current implementation > > of

On Sun, Sep 26, 2010 at 6:47 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > On Sun, Sep 26, 2010 at 3:28 PM, Michael Spencer <bigcheesegs at gmail.com> > wrote: >> >> On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords >> <blunted2night at gmail.com> wrote: >> > Hi guys, >> > While trying to get dwarf debugging information to work

On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > Hi guys, > While trying to get dwarf debugging information to work with Win32 COFF > targets, I came across a couple of issues with the current implementation > of WinCOFFObjectWriter. Emitting empty section causes debug information to > invalid, as the presence of certain debug section

On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > Hi guys, > While trying to get dwarf debugging information to work with Win32 COFF > targets, I came across a couple of issues with the current implementation > of WinCOFFObjectWriter. Emitting empty section causes debug information to > invalid, as the presence of certain debug section

On Tue, Sep 28, 2010 at 7:39 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: > On Sun, Sep 26, 2010 at 5:27 PM, Nathan Jeffords > <blunted2night at gmail.com> wrote: >> Hi guys, >> While trying to get dwarf debugging information to work with Win32 COFF >> targets, I came across a couple of issues with the current implementation >>

For those that are interested, I have attached the latest version of my Win32 COFF support patch. There is no new functionality, I just fixed some compiler errors due to recent changes in the MC library. - Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20100527/23598d23/attachment.html>

Hi guys, I have attached my patch to support generating win32 COFF object files. I would have posted earlier, but my system drive crashed and I had to rebuild my system; Luckily, my source code was on a secondary drive. I think this would be a good beginning for ongoing support of the COFF object file format and was hoping for some feedback as to whether it was commit worthy or what was needed to

On Mon, Jun 21, 2010 at 3:15 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > write_uint32_le is used to write into a arbitrary data buffer, where as >  WriteLE32 is used to write into the object file. Ah, I didn't notice that. Here's yet another style patch. Thanks to coppro for the review that found most of these. (note, I made a branch and did a rebase just so I

On Mon, Jun 21, 2010 at 9:37 AM, Aaron Gray <aaronngray.lists at gmail.com> wrote: > > Whats going on with having both write_uint32_le() > in WinCOFFObjectWriter::DefineSection() and WriteLE32() in > WinCOFFObjectWriter::WriteFileHeader() ? > Aaron Thanks, missed that one. Nathan used write_uint32_le in WinCOFF.h, and I guess accidentally used it in WinCOFFObjectWriter.cpp.

On 28 May 2010 05:59, Nathan Jeffords <blunted2night at gmail.com> wrote: > For those that are interested, I have attached the latest version of my > Win32 COFF support patch. There is no new functionality, I just fixed some > compiler errors due to recent changes in the MC library. > > Nathan, Sorry about this but... On Cygwin with GCC-4.2.4 :- In file included from

I have updated my patch based on Chris'es feedback. I removed the dbgout_calls macro, but left others in place for now. If there are no objections, I would like to commit this tomorrow evening (~7PM GMT-7). I have compiled and tested it on MSVC, with Michaels testing code and it looks good. Once this is committed, Michaels patch can be applied. -Nathan -------------- next part --------------

write_uint32_le is used to write into a arbitrary data buffer, where as WriteLE32 is used to write into the object file. On Mon, Jun 21, 2010 at 9:01 AM, Michael Spencer <bigcheesegs at gmail.com>wrote: > On Mon, Jun 21, 2010 at 9:37 AM, Aaron Gray <aaronngray.lists at gmail.com> > wrote: > > > > Whats going on with having both write_uint32_le() > > in

On Wed, Jun 9, 2010 at 11:11 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > This is cool, I was looking into something like this, but hit a little bit > of a wall, and then got sidetracked on another project. I was going to use > llc to generate COFF object files as opposed to clang. Seems to me llc would > give better control over what was generated and would also not

Hi all, Here is the latest revision of my Win32 COFF Support patch. This version includes changes based on Eli's feedback, and an implementation of weak reference symbols (COFF weak externals). If there is nothing major wrong with it, I would like to commit it. I can understand the lack of automated regression testing being one of those reasons. If so, can I have some guidance on how to

On Wed, May 5, 2010 at 9:38 PM, Chris Lattner <clattner at apple.com> wrote: > On May 5, 2010, at 6:44 PM, Nathan Jeffords wrote: > > ... >> Thanks, applied in r103150! llvm-mc -filetype=obj probably needs a >> similar patch. >> >> > cool!, I will make that change and submit it too. > > > Thanks! > > After looking into this, I have found

On Jun 14, 2010, at 3:41 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: > Michael, > > I have not made any changes since I last posted a patch. If you > would like to make the final updates, thats fine by me. I don't mind > making the changes either, I can have them done this evening as well. I'll let you do it then, along with sorting out the macros.

Nathan Jeffords <blunted2night at gmail.com> writes: > For those that are interested, I have attached the latest version of my > Win32 COFF support patch. There is no new functionality, I just fixed some > compiler errors due to recent changes in the MC library. Thanks Nathan. Any objections for not accepting the patch into LLVM? If none, I'll apply it after the weekend.

Thanks for the feedback. The line for commit-worthy is a round of reviews and some tests > showing that basic functionality works. > Regarding tests, I would like to have some form of automated regression testing, but am not sure how to go about doing so. My current testing involves running through my compilers regression test (compiles links and executes a number of test sources) and

On Wed, Jun 16, 2010 at 1:46 PM, Daniel Dunbar <daniel at zuster.org> wrote: > - Please split the patch into at least four parts: > (1) Add WinCOFFStreamer, with a stub implementation. > (2) Add WinCOFFObjectWriter, with a stub implementation. > (3) Fill in WinCOFFStreamer. > (4) Fill in WinCOFFObjectWriter. Attached is patch number 4. - Michael Spencer

On Sun, Jun 13, 2010 at 4:43 PM, Nathan Jeffords <blunted2night at gmail.com> wrote: >> I know some people are working on native linkers for LLVM. It would be >> interesting to see an architecture for handling object files that >> could be shared between lib/MC and a linker. > > > This would be good I think. > If a linker loaded object files into an IR, maybe