Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: linux-sparse@vger.kernel.org
Cc: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: [PATCH 0/7] move arch-specific builtins to their own table
Date: Wed, 10 Jun 2020 22:27:28 +0200	[thread overview]
Message-ID: <20200610202735.84968-1-luc.vanoostenryck@gmail.com> (raw)

The goal of this to avoid the declaration of arch-specific builtins
when the architecture doesn't match. As nice side-effects it also:
* add support for arch-specific builtins in their target-<arch>.c
* let these builtins declarations be done via a table (it was done
  via a serie of function calls, one by builtin).
* add minimal support for the architectures Alpha, Blackfin & Nios2.

These changes are motivated by a recent report from the kbuild test
bot (which seems to find lately much more sparse-related issues
in the kernel than it used to, often address-space & endianness
problems).


Luc Van Oostenryck (7):
  builtin: can be initialized later
  builtin: use a table for the builtins
  builtin: unify the 2 tables of builtins
  builtin: add support for arch-specific builtins
  arch: add specificities for Nios2
  arch: add specificities for Blackfin
  arch: add specificities for Alpha

 Makefile       |   3 +
 builtin.c      | 439 ++++++++++++++++++++++---------------------------
 builtin.h      |  15 ++
 lib.c          |   2 +-
 machine.h      |   5 +
 symbol.c       |   1 -
 symbol.h       |   1 -
 target-alpha.c |  30 ++++
 target-bfin.c  |  26 +++
 target-nios2.c |  31 ++++
 target.c       |   6 +
 target.h       |   7 +
 12 files changed, 321 insertions(+), 245 deletions(-)
 create mode 100644 builtin.h
 create mode 100644 target-alpha.c
 create mode 100644 target-bfin.c
 create mode 100644 target-nios2.c


base-commit: 42323db3955557b223268ec4196acb77308ab204
-- 
2.27.0

             reply	other threads:[~2020-06-10 20:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-10 20:27 Luc Van Oostenryck [this message]
2020-06-10 20:27 ` [PATCH 1/7] builtin: can be initialized later Luc Van Oostenryck
2020-06-12  0:50   ` Ramsay Jones
2020-06-10 20:27 ` [PATCH 2/7] builtin: use a table for the builtins Luc Van Oostenryck
2020-06-12  0:56   ` Ramsay Jones
2020-06-12 16:48     ` Luc Van Oostenryck
2020-06-10 20:27 ` [PATCH 3/7] builtin: unify the 2 tables of builtins Luc Van Oostenryck
2020-06-12  1:01   ` Ramsay Jones
2020-06-10 20:27 ` [PATCH 4/7] builtin: add support for arch-specific builtins Luc Van Oostenryck
2020-06-10 20:27 ` [PATCH 5/7] arch: add specificities for Nios2 Luc Van Oostenryck
2020-06-12  1:04   ` Ramsay Jones
2020-06-12 17:04     ` Luc Van Oostenryck
2020-06-10 20:27 ` [PATCH 6/7] arch: add specificities for Blackfin Luc Van Oostenryck
2020-06-10 20:27 ` [PATCH 7/7] arch: add specificities for Alpha Luc Van Oostenryck

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=20200610202735.84968-1-luc.vanoostenryck@gmail.com \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.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