Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
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 14:09:45 +0100	[thread overview]
Message-ID: <20200703130945.GA16144@blade.nx> (raw)
In-Reply-To: <70597daf-9f55-fff8-6503-7602c204028a@palves.net>

Pedro Alves wrote:
> On 7/3/20 10:30 AM, Gary Benson wrote:
> > 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?
> 
> What do you mean by "this"?  If you mean, the proposed change
> instead of:
> 
>     param_reg (120, 130, 32000, 33000);
>  -  param_reg (130, 120, 33000, 32000);
>  +  param_reg (-130, 120, -33000, 32000);
> 
> It's just that -130 and -33000 overflows, so I swapped the
> numbers back.

Cool, thank you.

Cheers,
Gary

-- 
Gary Benson - he / him / his
Principal Software Engineer, Red Hat



  reply	other threads:[~2020-07-03 13:09 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
2020-07-03 10:42     ` Pedro Alves
2020-07-03 13:09       ` Gary Benson [this message]
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=20200703130945.GA16144@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