From: Jan Beulich <jbeulich@suse.com>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: binutils@sourceware.org, gcc@gcc.gnu.org,
mingw-w64-public@lists.sourceforge.net
Subject: Re: Problems when building NT kernel drivers with GCC / LD
Date: Mon, 31 Oct 2022 10:55:59 +0100 [thread overview]
Message-ID: <9c878a09-fd84-325c-771a-65d88aff7282@suse.com> (raw)
In-Reply-To: <20221030000611.ytfadi4f2xcvodey@pali>
On 30.10.2022 02:06, Pali Rohár via Binutils wrote:
> * GCC or LD (not sure who) sets memory alignment characteristics
> (IMAGE_SCN_ALIGN_MASK) into the sections of PE executable binary.
> These characteristics should be only in COFF object files, not
> executable binaries. Specially they should not be in NT kernel
> drivers.
Like Martin pointed out in reply for another item, I'm pretty sure
this one was taken care of in bfd already (and iirc is in 2.39). You
fail to mention at all what versions of the various components you
use. I guess before reporting such a long list of issue you would
have wanted to test at least with the most recent releases of each
of the involved components. I wouldn't exclude some further items
could then be scratched off your list.
Jan
next prev parent reply other threads:[~2022-10-31 9:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 0:06 Pali Rohár
2022-10-30 7:06 ` [Mingw-w64-public] " Martin Storsjö
2022-10-30 19:58 ` ralph engels
2022-10-31 9:55 ` Jan Beulich [this message]
2022-11-05 0:57 ` Pali Rohár
2022-11-05 1:26 ` Pali Rohár
2022-11-20 13:10 ` Pali Rohár
2022-11-21 7:24 ` Jan Beulich
2022-11-26 19:04 ` Pali Rohár
2022-11-28 8:07 ` Jan Beulich
2022-11-28 8:40 ` Jonathan Wakely
2022-11-28 9:06 ` Jan Beulich
2022-12-26 10:47 ` Pali Rohár
2023-01-03 11:06 ` Nick Clifton
2023-02-20 18:25 ` Pali Rohár
2023-04-01 9:23 ` Pali Rohár
2023-04-12 9:53 ` Nick Clifton
2023-04-12 20:40 ` Pali Rohár
2024-01-07 1:55 ` Pali Rohár
2024-04-07 23:20 ` Pali Rohár
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=9c878a09-fd84-325c-771a-65d88aff7282@suse.com \
--to=jbeulich@suse.com \
--cc=binutils@sourceware.org \
--cc=gcc@gcc.gnu.org \
--cc=mingw-w64-public@lists.sourceforge.net \
--cc=pali.rohar@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).