similar to: [LLVMdev] python usage for test cases

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 2 May 2010 19:32, Nathan Jeffords <blunted2night at gmail.com> wrote: > Thanks for both of your feedback, I will attempt to make it fit LLVM coding > standards better before I resubmit my work. You can send me early drafts to run past GCC, send me something that works. As far as the hooks I put in, they are really only there so I could build > the object exporter outside of

Thanks for both of your feedback, I will attempt to make it fit LLVM coding standards better before I resubmit my work. As far as the hooks I put in, they are really only there so I could build the object exporter outside of LLVM, I think having it built directly in like others is preferable in the end. I do think it would be useful if projects had the option of extending supported formats

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 2 May 2010 10:53, Anton Korobeynikov <anton at korobeynikov.info> wrote: > Hello, Nathan > I'll let others comment on MC hooks, I just made a very brief look > over the contents of the archive. You can find the comments below. > Yes I looked at this and there are several ways but TargetAsmBackend looked the bast place to deal with the MCStreamer choice for different

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.

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, May 2, 2010 at 1:47 PM, Aaron Gray <aaronngray.lists at googlemail.com>wrote: > On 2 May 2010 19:32, Nathan Jeffords <blunted2night at gmail.com> wrote: > >> Thanks for both of your feedback, I will attempt to make it fit LLVM >> coding standards better before I resubmit my work. > > > You can send me early drafts to run past GCC, send me something

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

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>

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 require clang to be in the tree. Is there any documentation on how to run these tests from windows? - Nathan

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 implies available information, and emission of labels as symbols confused gdb about the structure of the program. The

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 Fri, May 28, 2010 at 4:28 PM, Eli Friedman <eli.friedman at gmail.com> wrote: > > Any objections for not accepting the patch into LLVM? If none, I'll > > apply it after the weekend. > > There should minimally be a bare-bones test to make sure that basic > COFF writer functionality doesn't crash.  Besides that, I don't see > any issues. I was looking

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

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

On May 6, 2010, at 11:22 PM, Nathan Jeffords wrote: > Thanks! Funny, I was just preparing a patch to submit for my changes to MCSectionCOFF. My changes look to be fairly independent of yours, my change was to deal with COMDAT's. I had dealt with the characteristics flags in the object writer, but I like this. If you don't mind I would like to merge my changes into this patch and submit

On Fri, May 7, 2010 at 12:05 AM, Chris Lattner <clattner at apple.com> wrote: > > On May 6, 2010, at 11:22 PM, Nathan Jeffords wrote: > > Thanks! Funny, I was just preparing a patch to submit for my changes to > MCSectionCOFF. My changes look to be fairly independent of yours, my change > was to deal with COMDAT's. I had dealt with the characteristics flags in the >

On Wed, Sep 12, 2012 at 12:19 PM, Manu <turkeyman at gmail.com> wrote: > On 12 September 2012 20:49, Nathan Jeffords <blunted2night at gmail.com>wrote: > >> >> On Wed, Sep 12, 2012 at 9:46 AM, Manu <turkeyman at gmail.com> wrote: >> >>> /Z7, that's the one. Maybe this approach can be used by LLVM? I presume >>> LLVM is capable of

Oops, I've managed to exclude the list... On 12 September 2012 19:28, Nathan Jeffords <blunted2night at gmail.com> wrote: > > > On Wed, Sep 12, 2012 at 8:50 AM, Manu <turkeyman at gmail.com> wrote: > >> On 12 September 2012 18:19, Nathan Jeffords <blunted2night at gmail.com>wrote: >> >>> This project seems to have some ability to convert to