From: Hans-Peter Nilsson <hp@bitrange.com>
To: Joshua Hudson <joshudson@gmail.com>
Cc: bug-binutils@gnu.org, binutils@sourceware.org
Subject: Re: PE header copyright issue
Date: Sun, 17 Dec 2023 13:14:42 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2312171308020.53469@arjuna.pair.com> (raw)
In-Reply-To: <CA+jjjYR7LDUkO8-Q08V9eC9_dQsTPgPn+dD4E7eyc1VY4B9=Qg@mail.gmail.com>
On Fri, 15 Dec 2023, Joshua Hudson wrote:
> I started looking into EFI64 development for reasons, and discovered
> something totally unexpected. The Debian grub64 loader and shim both
> start with some ancient MS-owned code, and the code is obviously the
> same stupid MS owned code that MS uses in their build tools since
> forever, and we can tell this because of an ancient bad bit of code
> writing in it. I researched the provenance of the 16 bit code and
> found what I expected; it was blindly imported by the original
> development of binutils-pe32 output target by looking at the output of
> the MS linker without understanding it.
Wow.
> I re-developed the stub 16 bit code, and prepared a patch to replace
> the MS own code with my own.
Good.
> I tested this by placing it after the 64 byte header lifted from
> debian grub EFI, resulting in a 117 byte binary (trailing zeros were
> eaten by the build pathway), and ran it in Dosbox to verify the error
> message appears as expected.
>
> Patch signed off by Joshua Hudson <joshudson@gmail.com>
<patch elided>
Could you please add the assembly source too?
Even if only as comments next to the corresponding byte-wise
contents of default_dos_message[] would be nice.
brgds, H-P
PS. binutils@sourceware.org address is the preferred address.
next parent reply other threads:[~2023-12-17 18:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CA+jjjYR7LDUkO8-Q08V9eC9_dQsTPgPn+dD4E7eyc1VY4B9=Qg@mail.gmail.com>
2023-12-17 18:14 ` Hans-Peter Nilsson [this message]
2023-12-17 21:20 ` Joshua Hudson
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=alpine.BSF.2.20.16.2312171308020.53469@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=binutils@sourceware.org \
--cc=bug-binutils@gnu.org \
--cc=joshudson@gmail.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).