public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Tom Tromey <tom@tromey.com>,
	Tom de Vries via Gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH v2 1/5] [gdb/symtab] Factor out compunit_epilogue_unwind_valid
Date: Mon, 20 Feb 2023 11:27:18 +0100	[thread overview]
Message-ID: <7defd3d5-2a47-85e7-c511-95e834ecb5b1@suse.de> (raw)
In-Reply-To: <9aac3a4f-de36-6dec-d4ea-c4b7c84ac75c@suse.de>

On 2/14/23 23:36, Tom de Vries via Gdb-patches wrote:
> On 2/14/23 16:56, Tom Tromey wrote:
>>>>>>> "Tom" == Tom de Vries via Gdb-patches 
>>>>>>> <gdb-patches@sourceware.org> writes:
>>
>> Tom> Factor out compunit_epilogue_unwind_valid from both
>> Tom> amd64_stack_frame_destroyed_p and i386_stack_frame_destroyed_p.  
>> NFC.
>>
>> What does NFC means?
>>
> 
> No Functional Changes.
> 
> I guess I picked this up when working on clang/llvm.
> 
> Mentioned here: https://llvm.org/docs/Lexicon.html#n .
> 

And grepping through the commit log, I see I used it before.

Anyway, replaced by "No functional changes".

>> Tom> Also add a comment in the new function about the assumption that 
>> in absence of
>> Tom> producer information, epilogue unwind info is invalid.
>>
>> Thanks.
>> Approved-By: Tom Tromey <tom@tromey.com>
>>

Thanks, I've added the tag to this commit and will commit the series 
after retesting.

Thanks,
- Tom


  reply	other threads:[~2023-02-20 10:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-13 14:23 [PATCH v2 0/5] [gdb/symtab] Assume epilogue unwind info is valid unless gcc < 4.5.0 Tom de Vries
2023-02-13 14:23 ` [PATCH v2 1/5] [gdb/symtab] Factor out compunit_epilogue_unwind_valid Tom de Vries
2023-02-14 15:56   ` Tom Tromey
2023-02-14 22:36     ` Tom de Vries
2023-02-20 10:27       ` Tom de Vries [this message]
2023-02-13 14:23 ` [PATCH v2 2/5] [gdb/tdep] Fix amd64/i386_stack_frame_destroyed_p Tom de Vries
2023-02-13 14:23 ` [PATCH v2 3/5] [gdb/tdep] Add amd64/i386 epilogue override unwinders Tom de Vries
2023-02-13 14:23 ` [PATCH v2 4/5] [gdb/symtab] Trust epilogue unwind info for unknown producer (-g0 case) Tom de Vries
2023-02-13 14:23 ` [PATCH v2 5/5] [gdb/symtab] Trust epilogue unwind info for unknown or non-gcc producer Tom de Vries

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=7defd3d5-2a47-85e7-c511-95e834ecb5b1@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=tom@tromey.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).