public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
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, 10 Oct 2022 23:58:37 +0300 (EEST)	[thread overview]
Message-ID: <7b501aa5-59b-5096-b192-7ccb38bbbfc@martin.st> (raw)
In-Reply-To: <8635e66a-3481-b3af-c620-18b9ce575a67@harmstone.com>

On Mon, 10 Oct 2022, Mark Harmstone wrote:

> Sorry Martin, I didn't quite get what you meant before. Yes, that's 
> fine; I'll resubmit with your changes.

Ok, great!

So after this, both lld and binutils would support these usage forms:

Preferred ones:
     -Wl,--pdb=<filename>
     -Wl,--pdb=     (implying the PDB filename from the output name)

Also supported (and used across third party code) but less ideal:
     -Wl,--pdb,<filename>

We could try to discourage (soft-deprecate?) the latter form and try to 
change most accessible third party projects to use the former form which 
is less ambiguous.

If we get most projects switched to using the preferred forms, and enough 
time passes (say a year or two?) we could maybe consider to remove support 
for the other form, leaving the door open for taking that into use as 
"-Wl,--pdb" as a less awkward form for the implicit output name, at some 
point in the future.

// Martin


  reply	other threads:[~2022-10-10 20:58 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 ` [PATCH 1/2] ld: Add --pdb option Martin Storsjö
2022-10-03 16:57   ` 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ö [this message]
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=7b501aa5-59b-5096-b192-7ccb38bbbfc@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).