From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: Jeff Law <law@redhat.com>,
"gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
Richard Biener <rguenther@suse.de>,
Jakub Jelinek <jakub@redhat.com>,
Alexandre Oliva <oliva@adacore.com>
Subject: Re: [PATCH] Add line debug info for virtual thunks (PR ipa/97937)
Date: Wed, 6 Jan 2021 08:52:40 +0100 [thread overview]
Message-ID: <AM0PR0602MB3410735E38B56F76B33FCAF6E4D00@AM0PR0602MB3410.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <6fe16e71-1a72-2c9d-11f2-642f9da8539b@redhat.com>
On 1/4/21 10:45 PM, Jeff Law wrote:
>
>
> On 1/4/21 1:06 PM, Bernd Edlinger wrote:
>> --- a/gcc/final.c
>> +++ b/gcc/final.c
>> @@ -1735,7 +1735,12 @@ final_start_function_1 (rtx_insn **firstp, FILE *file, int *seen,
>> last_filename);
>>
>> if (!dwarf2_debug_info_emitted_p (current_function_decl))
>> - dwarf2out_begin_prologue (0, 0, NULL);
>> + {
>> + if (write_symbols == DWARF2_DEBUG)
>> + dwarf2out_begin_prologue (last_linenum, last_columnnum, last_filename);
>> + else
>> + dwarf2out_begin_prologue (0, 0, NULL);
>> + }
> The only way you're getting into this code is for DEBUG_DWARF2 and
> VMS_AND_DWARF2_DEBUG and in the latter case we want to make the same
> fix. So drop the newly added conditional and just make the code
> something like this:
>
>
> if (!dwarf2_debug_info_emitted_p (current_function_decl))
> Â dwarf2out_begin_prologue (last_linenum, last_columnnum, last_filename)
>
>
No, this is block is entered iff
(write_symbols != DWARF2_DEBUG && write_symbols != VMS_AND_DWARF2_DEBUG)
|| DECL_IGNORED (current_function_decl))
so emitting .loc info here could easily break DBX, XCOFF, and VMS w/o DWARF
while I have no way to test anything for these debug formats.
Bernd.
next prev parent reply other threads:[~2021-01-06 7:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 20:06 Bernd Edlinger
2021-01-04 21:45 ` Jeff Law
2021-01-06 7:52 ` Bernd Edlinger [this message]
2021-01-05 12:26 ` Richard Biener
2021-01-06 7:01 ` Alexandre Oliva
2021-01-06 7:36 ` Bernd Edlinger
2021-01-06 7:50 ` Richard Biener
2021-01-06 10:07 ` Jakub Jelinek
2021-01-07 7:27 ` Richard Biener
2021-01-05 13:09 ` Alexandre Oliva
2021-01-06 11:49 ` Eric Botcazou
2021-01-06 12:26 ` Bernd Edlinger
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=AM0PR0602MB3410735E38B56F76B33FCAF6E4D00@AM0PR0602MB3410.eurprd06.prod.outlook.com \
--to=bernd.edlinger@hotmail.de \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=law@redhat.com \
--cc=oliva@adacore.com \
--cc=rguenther@suse.de \
/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).