public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
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, 21 Nov 2022 08:24:36 +0100	[thread overview]
Message-ID: <f20deff9-9cd1-3742-070f-0075d32b6b88@suse.com> (raw)
In-Reply-To: <20221120131057.mwk4nkl53vs4nygo@pali>

On 20.11.2022 14:10, Pali Rohár wrote:
> On Saturday 05 November 2022 02:26:52 Pali Rohár wrote:
>> On Saturday 05 November 2022 01:57:49 Pali Rohár wrote:
>>> On Monday 31 October 2022 10:55:59 Jan Beulich wrote:
>>>> 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.
>>>
>>> Ou, sorry for that. I take care to write issues in all details and
>>> totally forgot to write such important information like tool versions.
>>>
>>> Now I retested all issues on Debian 11 which has LD 2.35.2 and GCC
>>> 10.2.1 and all issues are there still valid except data characteristic
>>> IMAGE_SCN_CNT_INITIALIZED_DATA for code sections IMAGE_SCN_CNT_CODE.
>>>
>>> I can easily retest it with LD 2.39 and GCC 10.3.0 which is in Debian
>>> testing.
>>
>> Retested with LD 2.39 and GCC 10.3.0 which is in Debian testing and
>> following problems are additionally fixed: --exclude-all-symbols,
>> --dynamicbase and IMAGE_SCN_ALIGN_MASK (which you mentioned above). All
>> other still reminds.
>>
>> Do you need some other information?
> 
> Hello! I would like to ask if you need some other details or something
> else for these issues.

Well, generally speaking it might help if you could provide smallish
testcases for every item individually. But then, with you replying to
me specifically, perhaps you're wrongly assuming that I would be
planning to look into addressing any or all of these? My earlier reply
was merely to point out that _some_ work has already been done ...

Jan

  reply	other threads:[~2022-11-21  7:24 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
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 [this message]
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=f20deff9-9cd1-3742-070f-0075d32b6b88@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).