From: "Martin Storsjö" <martin@martin.st>
To: Mark Harmstone <mark@harmstone.com>
Cc: binutils@sourceware.org
Subject: Re: [PATCH 1/2] ld: Add --pdb option
Date: Mon, 3 Oct 2022 08:12:49 +0300 (EEST) [thread overview]
Message-ID: <26dfc8b7-e89d-9212-da69-b05044d2d8a9@martin.st> (raw)
In-Reply-To: <20221003014313.28766-1-mark@harmstone.com>
Hi Mark,
On Mon, 3 Oct 2022, Mark Harmstone wrote:
> This patch adds the --pdb option to ld when linking PE files, which
> augments the existing CodeView record used for build IDs by adding a PDB
> filename. If no filename is provided, this defaults to the image name
> with the extension replaced by "pdb".
As I assume you're aware, lld's mingw port also supports PDB generation -
and the description of this option also sounds like it's chosen to match
lld's option for outputting PDB files - that's good!
The testcase only seemed to exercise the form --pdb=<explicitname>, so I
thought I'd ask just for clarity: I guess the other forms of specifying
the option, e.g. "--pdb <explicitname>" also does the same - same thing
for setting the option with just one leading dash, "-pdb=<explicitname>"
(I guess it's a getopt feature that allows that as long as it isn't
ambiguous with single-letter options?), as well as the form "-pdb=" or
"--pdb=" for requesting it to set the default name?
// Martin
next prev parent reply other threads:[~2022-10-03 5:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-03 1:43 Mark Harmstone
2022-10-03 1:43 ` [PATCH 2/2] ld: Add minimal pdb generation Mark Harmstone
2022-10-03 5:12 ` Martin Storsjö [this message]
2022-10-03 16:57 ` [PATCH 1/2] ld: Add --pdb option Mark Harmstone
2022-10-03 18:58 ` Martin Storsjö
2022-10-07 12:16 ` Martin Storsjö
2022-10-09 23:46 ` Mark Harmstone
2022-10-10 10:27 ` Martin Storsjö
2022-10-10 16:55 ` Mark Harmstone
2022-10-10 20:58 ` Martin Storsjö
2022-10-05 4:20 ` Alan Modra
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=26dfc8b7-e89d-9212-da69-b05044d2d8a9@martin.st \
--to=martin@martin.st \
--cc=binutils@sourceware.org \
--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).