public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom de Vries <tdevries@suse.de>
To: Mark Wielaard <mark@klomp.org>, Tom Tromey <tom@tromey.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Pass const frame_info_ptr reference for skip_[language_]trampoline
Date: Wed, 3 May 2023 20:07:50 +0200	[thread overview]
Message-ID: <872d854d-9eb1-d028-38a5-b7d010af309d@suse.de> (raw)
In-Reply-To: <20230503151127.GE19114@gnu.wildebeest.org>

On 5/3/23 17:11, Mark Wielaard wrote:
> On Wed, May 03, 2023 at 08:50:07AM -0600, Tom Tromey wrote:
>>>>>>> "Mark" == Mark Wielaard <mark@klomp.org> writes:
>>
>> Mark> It isn't clear why only in this one place g++ sees the issue (probably
>> Mark> because it can inlined enough code in this specific case).
>>
>> s/inlined/inline/
>>
>> Could you add a "Bug:" trailer with a link to the bugzilla entry?
> 
> Fixed typo and added Bug link.
> 
>      PR build/30413
>      Bug: https://sourceware.org/bugzilla/show_bug.cgi?id=30413
> 
>> Anyway, other than that nit, this looks ok to me.  It's a little
>> unfortunate we don't know why exactly this particular spot warns, but on
>> the other hand, the fix is harmless (actually an improvement) and we've
>> worked around plenty of compiler oddities before.
>>
>> Reviewed-By: Tom Tromey <tom@tromey.com>
> 
> Thanks, pushed with that added. So that the code compiles again.
> 
> In the bug Tom de Vries has some ideas to "fix" this more generically
> by changing the frame_info_ptr destructor to give the compiler even
> more visibility into what is happening, which might help prevent
> similar issues in the future if you don't want to change a pass by
> value by a pass by reference.
> 

Hi Mark,

thanks for fixing this.

I've submitted a patch at 
https://sourceware.org/pipermail/gdb-patches/2023-May/199342.html .

Indeed it's not a "fix" for the warning as such.

It's more a follow-up on the observation that the code that triggers the 
warning was introduced for a reason that's no longer valid, so we can 
just remove it and simplify the code, which then also "fixes" the warning.

Thanks,
- Tom


  reply	other threads:[~2023-05-03 18:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-02 18:34 Mark Wielaard
2023-05-03  0:33 ` Kevin Buettner
2023-05-03 14:50 ` Tom Tromey
2023-05-03 15:11   ` Mark Wielaard
2023-05-03 18:07     ` Tom de Vries [this message]
2023-05-03 19:18       ` Mark Wielaard

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=872d854d-9eb1-d028-38a5-b7d010af309d@suse.de \
    --to=tdevries@suse.de \
    --cc=gdb-patches@sourceware.org \
    --cc=mark@klomp.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).