From: Pete Batard <pete@akeo.ie>
To: grub-devel@gnu.org
Subject: Re: [PATCH] fs: remove implicit compiler calls to memset/memcpy
Date: Mon, 18 Apr 2016 14:03:13 +0200 [thread overview]
Message-ID: <5714CD01.4070907@akeo.ie> (raw)
In-Reply-To: <CAEaD8JMFCL75ynmkV7s3X6cNeMf0aA9JgqbD=aCPR=R+P=gO-A@mail.gmail.com>
On 2016.04.18 12:49, Vladimir 'phcoder' Serbinenko wrote:
> In any case it's
> not 2.02 material, so I put it lower in my priority list
Thanks for considering it further - much appreciated.
I should point out that there's obviously nothing blocking for me, so
I'm fine with any delay.
On 2016.04.18 12:36, Andrei Borzenkov wrote:
> It is just that no current grub maintainers
> is using MSVC so if you volunteer to step in it would be great.
I wouldn't mind, and that is something I have done before with libcdio
-- sadly that effort was stopped short of adding full Visual Studio
support (i.e. with with project files), but at least now the libcdio
codebase is fully compatible with MS compilers. My only issue is that
I'm very busy with various projects, so time constraints are a major factor.
Still, I have been benefiting greatly from GRUB and I do have additional
MSVC compatibility patches, especially the ones that have to do struct
packing, that I wouldn't mind seeing integrated in the source. So if it
can help, I'll see if I can take a stab at providing MSVC support for
the whole project. Overall, short of very specific quirks, I haven't
found much in the way of compiling the GRUB code with MSVC, so maybe the
effort required won't be that bad...
I'll keep you posted.
Regards,
/Pete
prev parent reply other threads:[~2016-04-18 12:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-10 13:52 [PATCH] fs: remove implicit compiler calls to memset/memcpy Pete Batard
2016-04-10 14:30 ` Vladimir 'phcoder' Serbinenko
2016-04-10 15:50 ` Pete Batard
2016-04-18 5:50 ` Vladimir 'phcoder' Serbinenko
2016-04-18 10:13 ` Pete Batard
2016-04-18 10:36 ` Andrei Borzenkov
2016-04-18 10:49 ` Vladimir 'phcoder' Serbinenko
2016-04-18 12:03 ` Pete Batard [this message]
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=5714CD01.4070907@akeo.ie \
--to=pete@akeo.ie \
--cc=grub-devel@gnu.org \
/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 NNTP newsgroup(s).