From: Mark Harmstone <mark@harmstone.com>
To: Jeff Law <jeffreyalaw@gmail.com>,
gcc-patches@gcc.gnu.org, martin@martin.st
Subject: Re: [PATCH v2] Add -gcodeview option
Date: Sun, 20 Nov 2022 16:54:27 +0000 [thread overview]
Message-ID: <0f2259cf-4c67-6d2a-01ea-6e013248cab0@harmstone.com> (raw)
In-Reply-To: <435ca5c4-e680-7aa1-b9ac-e28bbbff7334@gmail.com>
On 20/11/22 16:43, Jeff Law wrote:
>
> On 10/26/22 21:38, Mark Harmstone wrote:
>> Changed to double dashes as per
>> https://gcc.gnu.org/pipermail/gcc-patches/2022-October/604287.html.
>
> What value is there in providing this option now? IIUC we don't have any of the bits yet to actually produce PDB records. It seems to me like this ought to be patch 1/n of a patch to produce PDB debug symbols.
This isn't useless, as ld will create symbols for the mangled names even without the .debug$S and .debug$T sections being present.
next prev parent reply other threads:[~2022-11-20 16:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-27 3:38 Mark Harmstone
2022-11-20 16:43 ` Jeff Law
2022-11-20 16:54 ` Mark Harmstone [this message]
2023-04-18 19:57 ` Jeff Law
2023-04-18 20:32 ` Jason Merrill
2023-04-18 20:51 ` Jeff Law
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=0f2259cf-4c67-6d2a-01ea-6e013248cab0@harmstone.com \
--to=mark@harmstone.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jeffreyalaw@gmail.com \
--cc=martin@martin.st \
/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).