public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: marxin <mliska@suse.cz>
To: gcc-patches@gcc.gnu.org
Subject: [PATCH 0/4] Clean-up warnings spotted by Rtags
Date: Mon, 24 Sep 2018 07:37:00 -0000	[thread overview]
Message-ID: <cover.1537774329.git.mliska@suse.cz> (raw)

Hello.

For quite some time I've been using Rtags for code completion and other
related stuff. Recently I noticed they provide diagnostics for an entire project.
Doing so, one can get quite some extra warning reported by Clang and I consider some
of them useful.

So that I would like to install my Python script that filters the warnings and few
patches that address the relevant warnings seen.

Patch survives bootstrap and regression tests on ppc64le-linux-gnu machine.

Martin

marxin (4):
  Add filter-rtags-warnings.py script.
  Remove unused functions and fields.
  Fix small coding style issues (PR fortran/87394).
  Fix scaling of a sreal number.

 contrib/filter-rtags-warnings.py |  71 ++++++++++++++++
 gcc/alias.c                      |   9 --
 gcc/config/i386/i386.c           |  15 ----
 gcc/cp/name-lookup.c             |  15 ----
 gcc/cp/parser.c                  |   8 --
 gcc/dbgcnt.c                     |   2 +-
 gcc/diagnostic-show-locus.c      |   2 -
 gcc/dump-context.h               |   1 -
 gcc/dumpfile.c                   |   4 +-
 gcc/dwarf2out.c                  | 141 -------------------------------
 gcc/edit-context.c               |   3 +-
 gcc/fortran/decl.c               |   2 +-
 gcc/fortran/trans.c              |  20 -----
 gcc/gcov-tool.c                  |   2 +-
 gcc/go/gofrontend/escape.cc      |  20 ++---
 gcc/go/gofrontend/expressions.cc |   2 +-
 gcc/go/gofrontend/gogo.h         |   2 +-
 gcc/go/gofrontend/types.cc       |  13 +--
 gcc/go/gofrontend/types.h        |   2 +-
 gcc/go/gofrontend/wb.cc          |  10 +--
 gcc/godump.c                     |   2 +-
 gcc/graphite-sese-to-poly.c      |   8 --
 gcc/ipa-cp.c                     |  10 ---
 gcc/ipa-fnsummary.c              |   2 +-
 gcc/lra-constraints.c            |  27 ------
 gcc/tree-chrec.c                 |  47 -----------
 gcc/tree-if-conv.c               |  13 ---
 gcc/tree-ssa-coalesce.c          |  16 ----
 gcc/tree-ssa-pre.c               |   6 --
 gcc/tree-ssa-uninit.c            |  10 ---
 gcc/tree-vrp.c                   |  38 ---------
 31 files changed, 96 insertions(+), 427 deletions(-)
 create mode 100755 contrib/filter-rtags-warnings.py

-- 
2.19.0

             reply	other threads:[~2018-09-24  7:37 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-24  7:37 marxin [this message]
2018-09-24  7:37 ` [PATCH 3/4] Fix small coding style issues (PR fortran/87394) marxin
2018-09-24 14:39   ` Jeff Law
2018-09-24  7:37 ` [PATCH 4/4] Fix scaling of a sreal number marxin
2018-09-24 14:42   ` Jeff Law
2018-09-24  7:37 ` [PATCH 1/4] Add filter-rtags-warnings.py script marxin
2018-09-24 14:45   ` Jeff Law
2018-09-24  7:39 ` [PATCH 2/4] Remove unused functions and fields marxin
2018-09-24 14:42   ` Jeff Law
2018-09-25  7:18     ` Martin Liška
2018-09-25 12:31       ` Richard Biener
2018-09-25 13:40         ` Jeff Law
2018-09-26  9:01           ` Martin Liška
2018-09-27 11:18             ` Bernhard Reutner-Fischer
2018-10-03 16:46               ` Jeff Law
2018-10-03 19:35                 ` Bernhard Reutner-Fischer
2018-10-05  2:19                   ` Bernhard Reutner-Fischer
2018-10-05 13:41                     ` Martin Liška
2018-10-09  8:52                       ` [PATCH] Remove dead functions and fix VMS target by moving back some functions Martin Liška
2018-10-09 22:53                         ` Martin Jambor
2018-10-10 11:13                           ` Martin Liška
2018-10-10 11:17                             ` Martin Jambor
2018-10-18 23:55   ` [PATCH 2/4] Remove unused functions and fields Ian Lance Taylor
2018-10-22 13:05     ` Martin Liška
2018-10-22 17:50       ` Ian Lance Taylor

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=cover.1537774329.git.mliska@suse.cz \
    --to=mliska@suse.cz \
    --cc=gcc-patches@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).