qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Gautam Agrawal" <gautamnagrawal@gmail.com>,
	qemu-devel@nongnu.org, "Alex Bennée" <alex.bennee@linaro.org>
Cc: qemu-s390x@nongnu.org, cohuck@redhat.com, david@redhat.com,
	richard.henderson@linaro.org
Subject: Re: [PATCH v2] tests/tcg/s390x: Test overflow conditions
Date: Thu, 2 Jun 2022 08:42:06 +0200	[thread overview]
Message-ID: <f36d00d1-be66-6dc8-d0aa-37319b1f8e57@redhat.com> (raw)
In-Reply-To: <20220531183524.40948-1-gautamnagrawal@gmail.com>

On 31/05/2022 20.35, Gautam Agrawal wrote:
> Add a test to check for overflow conditions in s390x.
> This patch is based on the following patches :
> * https://git.qemu.org/?p=qemu.git;a=commitdiff;h=5a2e67a691501
> * https://git.qemu.org/?p=qemu.git;a=commitdiff;h=fc6e0d0f2db51
> 
> Signed-off-by: Gautam Agrawal <gautamnagrawal@gmail.com>
> ---
> Changes since v1:
> - Corrected the "long" data type to "long long"
> - Changed local variable name in overflow function to "res"
> 
>   tests/tcg/s390x/Makefile.target |  1 +
>   tests/tcg/s390x/overflow.c      | 58 +++++++++++++++++++++++++++++++++
>   2 files changed, 59 insertions(+)
>   create mode 100644 tests/tcg/s390x/overflow.c
> 
> diff --git a/tests/tcg/s390x/Makefile.target b/tests/tcg/s390x/Makefile.target
> index 3124172736..7f86de85b9 100644
> --- a/tests/tcg/s390x/Makefile.target
> +++ b/tests/tcg/s390x/Makefile.target
> @@ -16,6 +16,7 @@ TESTS+=shift
>   TESTS+=trap
>   TESTS+=signals-s390x
>   TESTS+=branch-relative-long
> +TESTS+=overflow
>   
>   VECTOR_TESTS=vxeh2_vs
>   VECTOR_TESTS+=vxeh2_vcvt
> diff --git a/tests/tcg/s390x/overflow.c b/tests/tcg/s390x/overflow.c
> new file mode 100644
> index 0000000000..1c59c2cb70
> --- /dev/null
> +++ b/tests/tcg/s390x/overflow.c
> @@ -0,0 +1,58 @@
> +#include <stdio.h>
> +
> +int overflow_add_32(int x, int y)
> +{
> +    int res;
> +    return __builtin_add_overflow(x, y, &res);
> +}
> +
> +int overflow_add_64(long long x, long long y)
> +{
> +    long long res;
> +    return __builtin_add_overflow(x, y, &res);
> +}
> +
> +int overflow_sub_32(int x, int y)
> +{
> +    int res;
> +    return __builtin_sub_overflow(x, y, &res);
> +}
> +
> +int overflow_sub_64(long long x, long long y)
> +{
> +    long long res;
> +    return __builtin_sub_overflow(x, y, &res);
> +}
> +
> +int a1_add = -2147483648;
> +int b1_add = -2147483648;
> +long long a2_add = -9223372036854775808ULL;
> +long long b2_add = -9223372036854775808ULL;
> +
> +int a1_sub;
> +int b1_sub = -2147483648;
> +long long a2_sub = 0L;
> +long long b2_sub = -9223372036854775808ULL;
> +
> +int main()
> +{
> +    int ret = 0;
> +
> +    if (!overflow_add_32(a1_add, b1_add)) {
> +        fprintf(stderr, "data overflow while adding 32 bits\n");
> +        ret = 1;
> +    }
> +    if (!overflow_add_64(a2_add, b2_add)) {
> +        fprintf(stderr, "data overflow while adding 64 bits\n");
> +        ret = 1;
> +    }
> +    if (!overflow_sub_32(a1_sub, b1_sub)) {
> +        fprintf(stderr, "data overflow while subtracting 32 bits\n");
> +        ret = 1;
> +    }
> +    if (!overflow_sub_64(a2_sub, b2_sub)) {
> +        fprintf(stderr, "data overflow while subtracting 64 bits\n");
> +        ret = 1;
> +    }
> +    return ret;
> +}

Thinking a little bit more about this, there is nothing specific to s390x in 
here, so I think we could even move this test to tests/tcg/multiarch/ so 
that other architectures benefit from this test as well...

Alex, would that be OK for you?

  Thomas



      parent reply	other threads:[~2022-06-02  6:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-31 18:35 [PATCH v2] tests/tcg/s390x: Test overflow conditions Gautam Agrawal
2022-06-01  9:43 ` David Hildenbrand
2022-06-01 15:52 ` Thomas Huth
2022-06-02  6:42 ` Thomas Huth [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=f36d00d1-be66-6dc8-d0aa-37319b1f8e57@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=david@redhat.com \
    --cc=gautamnagrawal@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-s390x@nongnu.org \
    --cc=richard.henderson@linaro.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 NNTP newsgroup(s).