public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: "Vincent R." <forumer@smartmobili.com>
To: Viktor Kutuzov <vkutuzov@accesssoftek.com>
Cc: <binutils@sourceware.org>
Subject: Re: [GOLD] Heads up. Gold for mingw.
Date: Tue, 06 Oct 2009 22:02:00 -0000	[thread overview]
Message-ID: <63423ce0c19f1c0c56f69d7e941a0d64@mail.smartmobili.com> (raw)
In-Reply-To: <6AE1604EE3EC5F4296C096518C6B77EEED793568@mail.accesssoftek.com>

On Tue, 6 Oct 2009 14:45:40 -0700, Viktor Kutuzov
<vkutuzov@accesssoftek.com> wrote:
> Hello everyone,
> 
> I have started working to make gold build and work for mingw (Windows).
> There are 4 areas need to get changed:
> 
> 1.	The plug-in shared libraries will be plug-in DLLs. This one is easy
and
> straight forward.
> 
> 2.	Windows memory mapping doesn't fit well the used memory mapping.
Mingw
> does not support mmap/munmap. I think of extracting memory mapping to a
> separate set of classes (one multi-platform abstract base class and 2
> platform-specific implementation classes).
> 
> 3.	Gathering read is not supported on Windows (unless we want to use
> overlapped I/O). I think of implementing a Windows-specific readv based
on
> a regular read for now. Later we can make it better if we will want to.
> 
> 4.	Make files to add a new mingw configuration. This one is also easy
and
> straight forward.
> 
> Does anybody else work on this?
> Does anybody else interesting in gold for Windows?
> Is there a better idea how to do this?
> 
> Cheers,
> Viktor

Last time I asked I was answered that GOLD was very specific to elf and
when I read announcment :

"gold only supports ELF targets such as GNU/Linux and other free
operating systems.  gold does not support Windows.  There is no
expectation that gold will ever support anything other than ELF
targets."

But I like this quote from Marc Twain : They did not know it was
impossible, so they did it!


  reply	other threads:[~2009-10-06 22:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-13 15:09 [PATCH] gold: add cast to gold_unreachable to workaround gcc giving invalid "no return statement" warnings Mikolaj Zalewski
2009-08-14  8:34 ` Ian Lance Taylor
2009-08-14  9:28   ` Mikolaj Zalewski
2009-08-14  9:36     ` Ian Lance Taylor
2009-08-31 21:49 ` [PATCH] Gold: Added R_ARM_ABS8 relocation Viktor Kutuzov
2009-08-31 23:52   ` Gold: Testsuite Viktor Kutuzov
2009-09-01  0:46     ` Ian Lance Taylor
2009-09-01  1:02       ` Viktor Kutuzov
2009-09-01  2:10         ` Ian Lance Taylor
     [not found]           ` <6AE1604EE3EC5F4296C096518C6B77EEE56FBF60@mail.accesssoftek.com>
2009-09-02  1:31             ` Viktor Kutuzov
2009-09-01  0:56   ` [PATCH] Gold: Added R_ARM_ABS8 relocation Ian Lance Taylor
2009-09-01 19:53     ` [PATCH Take 2] " Viktor Kutuzov
2009-09-01 21:24       ` Ian Lance Taylor
2009-09-02  1:30         ` [PATCH] Gold: Added R_ARM_ABS8 relocation unit test Viktor Kutuzov
2009-09-16  0:23           ` [PATCH] Gold: Added R_ARM_GOT_PREL relocation and unit tests Viktor Kutuzov
2009-09-16  1:00             ` [Gold] Heads up. Working on interworking Viktor Kutuzov
2009-10-06 21:46               ` [GOLD] Heads up. Gold for mingw Viktor Kutuzov
2009-10-06 22:02                 ` Vincent R. [this message]
2009-10-06 22:26                   ` Viktor Kutuzov
2009-10-06 22:06                 ` Matt Rice
2009-10-07 15:31             ` [PATCH] Gold: Added R_ARM_GOT_PREL relocation and unit tests Ian Lance Taylor
     [not found]         ` <6AE1604EE3EC5F4296C096518C6B77EEE56FBF62@mail.accesssoftek.com>
2009-09-03 23:26           ` [PATCH, Take 2] Gold: Added R_ARM_ABS8 relocation unit test Viktor Kutuzov
2009-09-27  7:35             ` Ian Lance Taylor
2009-09-29 23:30               ` Viktor Kutuzov
2009-09-29 23:40                 ` Ian Lance Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=63423ce0c19f1c0c56f69d7e941a0d64@mail.smartmobili.com \
    --to=forumer@smartmobili.com \
    --cc=binutils@sourceware.org \
    --cc=vkutuzov@accesssoftek.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).