From: Shengyu Huang <kumom.huang@gmail.com>
To: David Malcolm <dmalcolm@redhat.com>
Cc: GCC Development <gcc@gcc.gnu.org>
Subject: Re: [GSoC][Static Analyzer] Some questions and request for a small patch to work on
Date: Tue, 28 Feb 2023 10:18:06 +0100 [thread overview]
Message-ID: <E6C9A54D-1B7A-4380-9151-DF45BA544BF4@gmail.com> (raw)
In-Reply-To: <594374fad6f19b956b3f0e6e5ce04ad51205186b.camel@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1258 bytes --]
Hi Dave,
Do you want me to follow the steps 7-10 (https://gcc-newbies-guide.readthedocs.io/en/latest/how-to-improve-the-location-of-a-diagnostic.html) or tell you where I add the code simply? Basically, I added
warning_at (DECL_SOURCE_LOCATION (node->decl), 0, "hello world, I’m compiling %qE", node->decl);
to the loop of cgraph_node inside impl_run_checkrs (logger *logger) of analyzer/engine.cc <http://engine.cc/>.
(I also tried adding this code to cgraph_node::cgraphunit.cc <http://cgraphunit.cc/> in cgraphunit.cc <http://cgraphunit.cc/>, and then I found out the warning_at is different in that scope…but inform would work.)
Best,
Shengyu
P.S. Shall I continue put mailing list in my cc? Not sure the community wants to receive that many GSoC related emails.
> On 22 Feb 2023, at 16:43, David Malcolm <dmalcolm@redhat.com> wrote:
>
> Sorry, I was unclear; I was referring to this part of my guide:
> https://gcc-newbies-guide.readthedocs.io/en/latest/getting-started.html#hello-world-from-the-compiler
>
> i.e. try writing a new warning that simply emits something like:
>
> test.c:2:1: warning: hello world, I'm compiling 'main'
> 2 | int main ()
> | ^~~~
>
> for each function that it sees.
next prev parent reply other threads:[~2023-02-28 9:18 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-21 21:26 Shengyu Huang
2023-02-21 22:55 ` David Malcolm
2023-02-22 14:03 ` Jonathan Wakely
2023-02-23 11:17 ` James K. Lowden
2023-02-23 16:30 ` Jonathan Wakely
2023-02-22 14:11 ` Shengyu Huang
2023-02-22 14:53 ` Iain Sandoe
2023-02-22 15:13 ` Iain Sandoe
2023-02-27 13:35 ` Shengyu Huang
2023-02-27 13:45 ` Iain Sandoe
2023-02-27 13:51 ` Shengyu Huang
2023-02-27 13:49 ` Iain Sandoe
2023-02-27 14:01 ` Floyd, Paul
2023-02-22 15:43 ` David Malcolm
2023-02-28 9:18 ` Shengyu Huang [this message]
2023-02-28 23:59 ` David Malcolm
2023-03-01 11:16 ` Shengyu Huang
2023-03-01 13:48 ` David Malcolm
2023-02-28 14:46 ` [GSoC][Static Analyzer] Ideas for proposal Shengyu Huang
2023-03-01 0:22 ` David Malcolm
2023-03-12 22:20 ` Shengyu Huang
2023-03-13 15:51 ` David Malcolm
2023-03-20 17:28 ` [GSoC][Static Analyzer] First proposal draft and a few more questions/requests Shengyu Huang
2023-03-20 22:50 ` David Malcolm
2023-03-26 16:03 ` Shengyu Huang
2023-03-26 17:14 ` David Malcolm
2023-03-26 21:46 ` Shengyu Huang
2023-04-01 14:19 ` Shengyu Huang
2023-04-02 22:53 ` David Malcolm
2023-04-03 0:02 ` Shengyu Huang
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=E6C9A54D-1B7A-4380-9151-DF45BA544BF4@gmail.com \
--to=kumom.huang@gmail.com \
--cc=dmalcolm@redhat.com \
--cc=gcc@gcc.gnu.org \
/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).