public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Martin Storsjö" <martin@martin.st>
To: Mark Harmstone <mark@harmstone.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: [PATCH] Add -gcodeview option
Date: Tue, 25 Oct 2022 11:21:49 +0300 (EEST)	[thread overview]
Message-ID: <a22433f5-b4d2-19b7-86a2-31e2ee45fb61@martin.st> (raw)
In-Reply-To: <1842c5cf-ab33-c9f5-cee0-9d91512a330a@harmstone.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

On Tue, 25 Oct 2022, Mark Harmstone wrote:

> On 24/10/22 12:08, Martin Storsjö wrote:
>> Hmm, what does this end up passing to the linker in the end - does it just 
>> pass "-pdb="? (What does the "*" parameter do here?) If that's the case - 
>> that sounds reasonable - assuming that if a user passes an extra 
>> -Wl,--pdb,myspecificname.pdb, that would take precedence (i.e. be passed 
>> after the compiler's default one). 
>
> That's right. The "*" means "all languages".

Ok, great.

Btw, stylistically, should we strive towards using double dashes for the 
pdb option? I think that's the most canonical way for such getopt options 
(even though it doesn't make any practical difference). I've started 
trying to update various users to prefer that form (together with 
preferring -Wl,--pdb=<name> over -Wl,--pdb,<name>) and probably will send 
a few more.

// Martin

  reply	other threads:[~2022-10-25  8:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  0:28 Mark Harmstone
2022-10-24 11:08 ` Martin Storsjö
2022-10-24 23:20   ` Mark Harmstone
2022-10-25  8:21     ` Martin Storsjö [this message]
2022-10-27  3:36       ` Mark Harmstone

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=a22433f5-b4d2-19b7-86a2-31e2ee45fb61@martin.st \
    --to=martin@martin.st \
    --cc=gcc-patches@gcc.gnu.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).