From: "Six, Lancelot" <Lancelot.Six@amd.com>
To: Bruno Larsen <blarsen@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "lsix@lancelotsix.com" <lsix@lancelotsix.com>
Subject: RE: [PATCH v2 2/2] gdb: Respect the DW_CC_nocall attribute
Date: Mon, 31 Jan 2022 14:19:40 +0000 [thread overview]
Message-ID: <PH0PR12MB5452B69B2CFC3946B3634B1483259@PH0PR12MB5452.namprd12.prod.outlook.com> (raw)
In-Reply-To: <49c17cc9-fd06-31ea-b4f1-174c26b7eb9b@redhat.com>
[AMD Official Use Only]
Hi,
> > else if (thisfun != NULL)
> > {
> > + if (is_nocall_function (check_typedef (value_type (function))))
> > + query_prefix
> > + = string_printf ("The function '%s' does not follow the target "
> > + "calling convention.\n"
> > + "If you continue, setting the return value "
> > + "will probably lead to unpredictable "
> > + "behaviors.\n",
> > + thisfun->print_name ());
> > +
>
> I feel like this if statement could have a set of { } around it. The assignment and call are big enough to be confusing on a quick glance
Will do.
> > +
> > +int
> > +foo ()
> > +{
> > + asm ("foo_label: .globl foo_label");
> > + return 42;
> > +}
>
> According to the testsuite coding standards, this should be foo (void), instead of foo ()
OK
> > +if ![runto_main] {
> > + return -1
> > +}
>
> Following Keith Seitz's request to be more pedantic about TCL formatting, I think this should be
>
> if {![runto_main]} {
Will change that as well. Thanks for pointing this out.
Thanks for the feedbacks.
Best,
Lancelot.
> Like I said, I can't approve for pushing, but LGTM.
>
> --
> Cheers!
> Bruno Larsen
prev parent reply other threads:[~2022-01-31 14:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-28 14:29 [PATCH v2 0/2] Make GDB respect " Lancelot SIX
2022-01-28 14:29 ` [PATCH v2 1/2] gdb: Move most of get_function_name (COREADDR) in symtab.h Lancelot SIX
2022-01-31 13:17 ` Bruno Larsen
2022-01-28 14:29 ` [PATCH v2 2/2] gdb: Respect the DW_CC_nocall attribute Lancelot SIX
2022-01-31 13:19 ` Bruno Larsen
2022-01-31 14:05 ` Simon Marchi
2022-01-31 14:34 ` Six, Lancelot
2022-01-31 14:36 ` Simon Marchi
2022-01-31 14:19 ` Six, Lancelot [this message]
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=PH0PR12MB5452B69B2CFC3946B3634B1483259@PH0PR12MB5452.namprd12.prod.outlook.com \
--to=lancelot.six@amd.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lsix@lancelotsix.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).