From: Joe Perches <joe@perches.com>
To: "liaochang (A)" <liaochang1@huawei.com>,
Conor Dooley <conor.dooley@microchip.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, heiko.stuebner@vrull.eu,
ajones@ventanamicro.com, prabhakar.mahadev-lad.rj@bp.renesas.com,
jszhang@kernel.org, vincent.chen@sifive.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: Add header include guards to insn.h
Date: Wed, 01 Feb 2023 19:33:28 -0800 [thread overview]
Message-ID: <38d7d022d6e88d643c8037e26707a719cb55ff1d.camel@perches.com> (raw)
In-Reply-To: <f161df27-f2d7-0367-33a0-9ff5e4b880d9@huawei.com>
On Thu, 2023-02-02 at 08:52 +0800, liaochang (A) wrote:
>
> 在 2023/2/1 17:42, Conor Dooley 写道:
> > Hi,
> >
> > On Wed, Feb 01, 2023 at 05:37:24PM +0800, liaochang (A) wrote:
> > > 在 2023/1/30 22:53, Conor Dooley 写道:
> > > > On Sun, Jan 29, 2023 at 05:42:42PM +0800, Liao Chang wrote:
> > > > > Add header include guards to insn.h to prevent repeating declaration of
> > > > > any identifiers in insn.h.
> > > >
> > > > I'm curious, did you spot this "by hand" while doing other work, or do
> > > > you have a tool that found it for you?
> > >
> > > I found this "by hand", inspired by scripts/checkdeclares.pl, i write a tiny tool
> > > to analyse the missing header guards in header file.
> >
> > Ohh, cool! I'd love to add this one to the checks on patchwork so that
> > we do not end up adding any more of these. If this is based on
> > checkdeclares, is it GPLv2?
>
> Definitely, it is GPLv2,i will appending licence identifier and copyright info later.
>
> Hi,@Joe Perches, is it ok to integrate this tool to scripts?
Don't see why not.
Perhaps submit it as a real patch to Andrew Morton <akpm@linux-foundation.org>
Trivial notes below:
> > > #!/usr/bin/env perl
> > > use strict;
> > >
> > > sub usage {
> > > print "Usage: checkguards.pl file1.h ...\n";
> > > print "Warn of missing header guards\n";
> > > exit 1;
> > > }
> > >
> > > if ($#ARGV < 0) {
> > > usage();
> > > }
> > >
> > > foreach my $file (@ARGV) {
> > > open(my $f, '<', $file)
> > > or die "Cannot open $file: $!.\n";
> > >
> > > my $scan_area = 1;
> > > my $guards_warn = 0;
> > >
> > > # The lines of header file are divided into several areas as follows:
> > > #
> > > # ... area1 ...
> > > # #ifndef _HEADER_GUARD
> > > # ... area2 ...
> > > # #define _HEADER_GUARD
> > > # ... area3 ...
> > > # #endif /* _HEADER_GUARD */
> > > # ... area4 ...
> > > # EOF
> > > #
> > > # If any statement is found in area1, area2, and area4, it
> > > # throws a warning of illegal usage of header guard usage.
Not illegal, invalid
> > > while (<$f>) {
> > > if (m/^(.*);\s*$/o) {
> > > if ($scan_area == 1 || $scan_area == 2 || $scan_area == 4) {
> > > ++$guards_warn;
> > > }
> > > } elsif (m/^\s*(#ifndef\s+)[a-zA-Z0-9_]*_H[_]*\s*$/o) {
> > > ++$scan_area;
> > > } elsif (m/^\s*(#define\s+)[a-zA-Z0-9_]*_H[_]*\s*$/o) {
> > > ++$scan_area;
> > > } elsif (m/^\s*(#endif)\s*\/\*\s*[a-zA-Z0-9_]*_H[_]*\s*\*\/\s*$/o) {
> > > ++$scan_area;
> > > }
> > > }
> > >
> > > close($f);
> > >
> > > if ($guards_warn) {
> > > print "Illegal usage of header guard found in $file.\n";
here too
There are also uses like #if !defined(FOO)
There can be spaces before and after the #
It might also be useful to have a check for missing header guards.
next prev parent reply other threads:[~2023-02-02 3:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-29 9:42 Liao Chang
2023-01-30 7:35 ` Andrew Jones
2023-01-30 14:53 ` Conor Dooley
2023-02-01 9:37 ` liaochang (A)
2023-02-01 9:42 ` Conor Dooley
2023-02-02 0:52 ` liaochang (A)
2023-02-02 3:33 ` Joe Perches [this message]
2023-02-02 11:36 ` liaochang (A)
2023-02-22 15:00 ` patchwork-bot+linux-riscv
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=38d7d022d6e88d643c8037e26707a719cb55ff1d.camel@perches.com \
--to=joe@perches.com \
--cc=ajones@ventanamicro.com \
--cc=akpm@linux-foundation.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor.dooley@microchip.com \
--cc=heiko.stuebner@vrull.eu \
--cc=jszhang@kernel.org \
--cc=liaochang1@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=vincent.chen@sifive.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
all inboxes | Powered by JetHome®