linux-sparse.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>
Cc: Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH] asm-out0: fix a test failure on 32-bit systems
Date: Sun, 28 Feb 2021 22:31:57 +0100	[thread overview]
Message-ID: <20210228213157.nxqmkgtnr7czgzcd@mail> (raw)
In-Reply-To: <4626bf8c-6079-976a-f579-f76ed1d2792d@ramsayjones.plus.com>

On Sat, Feb 27, 2021 at 05:15:19PM +0000, Ramsay Jones wrote:
> 
> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> ---
> 
> Hi Luc,
> 
> So, I did some 32-bit testing this afternoon ... ;-)

Good :)
 
> The problem here being s/symaddr.64/symaddr.32/, of course. I did the
> minimum necessary to get it to work (adding the -m64), so no creative
> solutions here (not that I could think of any)!
> 
> [I suppose that I could also have created asm-out1.c as a copy and then
> done s/symaddr.64/symaddr.32/, s/-m64/-m32/, but I didn't.]

The ideal solution, at least from a functional point of view, would be
to change the "32" by something like "$POINTER_SIZE$" and doing the
substitution when comparing the files but that would complicate a bit
more the testing and make it slower. Another solution would simply to
add for such tests an option to not display the instruction's size.

In this case, what you did is, IMO, the correct solution because the test
is obviously not size dependent, it's just that the size is displayed.

Thanks,
-- Luc

      reply	other threads:[~2021-02-28 21:32 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-27 17:15 [PATCH] asm-out0: fix a test failure on 32-bit systems Ramsay Jones
2021-02-28 21:31 ` 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=20210228213157.nxqmkgtnr7czgzcd@mail \
    --to=luc.vanoostenryck@gmail.com \
    --cc=linux-sparse@vger.kernel.org \
    --cc=ramsay@ramsayjones.plus.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;
as well as URLs for NNTP newsgroup(s).