From: Nick Clifton <nickc@redhat.com>
To: "Pali Rohár" <pali.rohar@gmail.com>,
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: Tue, 3 Jan 2023 11:06:26 +0000 [thread overview]
Message-ID: <53f87e9a-3086-1f9c-5a9c-3e4f7c1555d6@redhat.com> (raw)
In-Reply-To: <20221226104758.ymu4vzkv7kl5jeqv@pali>
Hi Pali,
> Hello! I would like to remind this thread for gcc/binutils developers.
> Most of these issues are still present and cause problems for compiling
> native PE binary. If you have questions or you need any other information
> please let me know.
Have bug reports been filed for the individual issues ? If not, please
could they be created. The URLs for filing bugs are:
https://sourceware.org/bugzilla/enter_bug.cgi?product=binutils
https://gcc.gnu.org/bugzilla/enter_bug.cgi
It would *really* help if the bug reports include a simple test case
to reproduce the specific problems.
If it is not clear which tool is the source of the problem, then I would
suggest choosing the binutils first. If it turns out that specific issue
is actually caused by a problem in gcc, the bug report can always be moved
later on.
Cheers
Nick
next prev parent reply other threads:[~2023-01-03 11:06 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
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 [this message]
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=53f87e9a-3086-1f9c-5a9c-3e4f7c1555d6@redhat.com \
--to=nickc@redhat.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).