From: David Malcolm <dmalcolm@redhat.com>
To: mirimnan017@gmail.com, gcc-patches@gcc.gnu.org
Cc: Immad Mir <mirimmad@outlook.com>
Subject: Re: [PATCH] Adding three new function attributes for static analysis of file descriptors
Date: Tue, 19 Jul 2022 16:08:41 -0400 [thread overview]
Message-ID: <0f9319d622d9fe195d994e847c7d87a54f416e07.camel@redhat.com> (raw)
In-Reply-To: <1e44d1ae1933ed588ee91fbc296683a7428f18e6.camel@redhat.com>
On Tue, 2022-07-19 at 14:18 -0400, David Malcolm wrote:
> On Tue, 2022-07-19 at 21:36 +0530, Immad Mir wrote:
>
[...snip...]
>
>
> > +void
> > +fd_state_machine::check_for_fd_attrs (
> > + sm_context *sm_ctxt, const supernode *node, const gimple
> > *stmt,
> > + const tree callee_fndecl, const char *attr_name,
> > + access_directions fd_attr_access_dir) const
> > +{
I had another idea about the patch: we have attr_name here, and thus I
think it's available when creating the various fd_param_diagnostic
instances, so why not convert the:
bool m_attr;
in fd_param_diagnostic to:
const char *m_attr_name; // can be NULL if no attribute involved
and then, when it's non-NULL we can use it directly in the inform
message, so that the attribute name we report is the one that the user
used. I think that's clearer, both for us and for the end-user.
Dave
next prev parent reply other threads:[~2022-07-19 20:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 16:06 Immad Mir
2022-07-19 18:18 ` David Malcolm
2022-07-19 20:08 ` David Malcolm [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-07-22 15:55 Immad Mir
2022-07-22 18:27 ` David Malcolm
2022-07-20 17:59 Immad Mir
2022-07-20 18:23 ` David Malcolm
2022-07-20 18:28 ` Prathamesh Kulkarni
2022-07-20 18:39 ` Mir Immad
2022-07-15 15:38 Immad Mir
2022-07-15 16:57 ` David Malcolm
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=0f9319d622d9fe195d994e847c7d87a54f416e07.camel@redhat.com \
--to=dmalcolm@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mirimmad@outlook.com \
--cc=mirimnan017@gmail.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).