public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Nick Clifton <nickc@redhat.com>
To: Mark Harmstone <mark@harmstone.com>,
	binutils@sourceware.org, jbeulich@suse.com
Subject: Re: [PATCH v2] Add pdb archive target
Date: Fri, 9 Sep 2022 11:55:14 +0100	[thread overview]
Message-ID: <8a0ed098-8e53-f843-e40d-30e7122447bc@redhat.com> (raw)
In-Reply-To: <20220909001423.23938-1-mark@harmstone.com>

Hi Mark,

> See https://sourceware.org/pipermail/binutils/2022-July/122019.html for
> the original patch.
> 
> Changes from original:

> 
> * Reduced number of targets that pull this in by default

Patch approved, but with two caveats, one major, one minor:

   * Your new tests (thank you for including those) fail for targets
     which do not support the pdb archive format.  For example when
     I ran the binutils testsuite with a toolchain configured as
     --target=x86_64-pc-linux-gnu there were three new failures, all
     of which looked like this:

       binutils/.libs/ar: tmpdir/test.pdb: invalid bfd target

       FAIL: pdb archive 1

     So please could you add a test for supported targets at the start
     of the pdb.exp file ?  (See the start of dlltool.exp for an example
     of this).

   * Please could you update the comments in your C code so that they
     follow the GNU Coding Standard.  Ie:

       /* Comments start with a capital letter and end with a
          full stop followed by two spaces.  */

Cheers
   Nick


      reply	other threads:[~2022-09-09 10:55 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-09  0:14 Mark Harmstone
2022-09-09 10:55 ` Nick Clifton [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=8a0ed098-8e53-f843-e40d-30e7122447bc@redhat.com \
    --to=nickc@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=jbeulich@suse.com \
    --cc=mark@harmstone.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).