Linux SPARSE checker discussions
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Toomas Soome <tsoome@me.com>
Cc: John Levon <john.levon@joyent.com>, linux-sparse@vger.kernel.org
Subject: Re: [PATCH] correct sparcv9 defines
Date: Wed, 22 Jan 2020 23:48:01 +0100	[thread overview]
Message-ID: <20200122224801.piocizxa45ejy3zg@ltop.local> (raw)
In-Reply-To: <BFD5AC88-E262-4579-BBD4-3C2BBBEAEBF9@me.com>

On Wed, Jan 22, 2020 at 12:53:58PM +0200, Toomas Soome wrote:
> > On 21. Jan 2020, at 02:13, Luc Van Oostenryck <luc.vanoostenryck@gmail.com> wrote:
> > 
> > Thanks for the patch.
> > Is it possible to have Toomas' Signed-off-by for this patch?
> > No need to resend the patch, just a reply to this email
> > saying it's OK is enough.
> 
> OK by me:)
> 
> > 
> >> 	case MACH_SPARC32:
> >> 		predefine("__sparc__", 1, "1");
> >> 		predefine("__sparc", 1, "1");
> >> +		predefine("sparc", 1, "1");
> > 
> > I'm wondering if there is a real need for this one or if
> > it's just to reflect what GCC do? I'm a bit reluctant to
> > add it since it lies in the user's namespace. But I'm fine
> > to add it if there is a real use case for it (in which case
> > I'll just slightly change the patch to not predefine it if
> > one of the ISO dialect is selected (via --std=c99, ...)).
> > 
> 
> 
> The problem is that gcc does define those symbols and the code is using them, hence smatch should behave the same:

OK, fine for me if the symbol is effectively used.
This patch and John's are applied and pushed with some adaptations
for a related pending branch I merged first.

Thanks,
-- Luc

      parent reply	other threads:[~2020-01-22 22:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-20 10:38 [PATCH] correct sparcv9 defines john.levon
2020-01-21  0:13 ` Luc Van Oostenryck
     [not found]   ` <BFD5AC88-E262-4579-BBD4-3C2BBBEAEBF9@me.com>
2020-01-22 22:48     ` Luc Van Oostenryck [this message]

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=20200122224801.piocizxa45ejy3zg@ltop.local \
    --to=luc.vanoostenryck@gmail.com \
    --cc=john.levon@joyent.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=tsoome@me.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