From: Gary Benson <gbenson@redhat.com>
To: Pedro Alves <pedro@palves.net>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Make out of range type conversions explicit
Date: Fri, 3 Jul 2020 10:30:18 +0100 [thread overview]
Message-ID: <20200703093018.GB8482@blade.nx> (raw)
In-Reply-To: <bc933f07-bec8-1ff1-2e27-5f025ababfb7@palves.net>
Pedro Alves wrote:
> diff --git a/gdb/testsuite/gdb.base/structs2.c b/gdb/testsuite/gdb.base/structs2.c
> index 7c8be035221..aac7bce8c15 100644
> --- a/gdb/testsuite/gdb.base/structs2.c
> +++ b/gdb/testsuite/gdb.base/structs2.c
> @@ -13,7 +13,7 @@ main ()
>
> bkpt = 0;
> param_reg (120, 130, 32000, 33000);
> - param_reg (130, 120, 33000, 32000);
> + param_reg (-120, 130, -32000, 33000);
>
> return 0;
> }
On first glance I thought this was a copy-paste error. I don't think
it is, but, just in case, can you confirm the change above is what you
intended?
> diff --git a/gdb/testsuite/gdb.base/structs2.exp b/gdb/testsuite/gdb.base/structs2.exp
> index 8a7d9c69378..5722be3109c 100644
> --- a/gdb/testsuite/gdb.base/structs2.exp
> +++ b/gdb/testsuite/gdb.base/structs2.exp
> @@ -49,5 +49,5 @@ if [test_compiler_info gcc-3-*] {
> setup_xfail hppa*-* gcc/15860
> }
> gdb_test "continue" \
> - ".*pr_char=-126.*pr_uchar=120.*pr_short=-32536.*pr_ushort=32000.*bkpt = 1.*" \
> + ".*pr_char=-120.*pr_uchar=130.*pr_short=-32000.*pr_ushort=33000.*bkpt = 1.*" \
> "structs2 continue2"
--
Gary Benson - he / him / his
Principal Software Engineer, Red Hat
next prev parent reply other threads:[~2020-07-03 9:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-30 13:58 Gary Benson
2020-06-30 17:52 ` Luis Machado
2020-07-02 20:23 ` Pedro Alves
2020-07-03 9:30 ` Gary Benson [this message]
2020-07-03 10:42 ` Pedro Alves
2020-07-03 13:09 ` Gary Benson
2020-07-03 14:05 ` Pedro Alves
2020-07-07 11:37 ` Gary Benson
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=20200703093018.GB8482@blade.nx \
--to=gbenson@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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