Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Christian Biesinger via gdb-patches" <gdb-patches@sourceware.org>
To: Pedro Alves <palves@redhat.com>
Cc: Andrew Burgess <andrew.burgess@embecosm.com>,
	gdb-patches <gdb-patches@sourceware.org>
Subject: Re: [PUSHED] gdb: Use std::abs instead of abs on LONGEST types
Date: Thu, 27 Feb 2020 19:09:00 -0000	[thread overview]
Message-ID: <CAPTJ0XEz98WLdGw3=OHREEqg4HkLfs6CjVBFFYqxgbC3yGsL=w@mail.gmail.com> (raw)
In-Reply-To: <09b7ad54-6c4f-922e-9a72-9e3d26603aec@redhat.com>

On Thu, Feb 27, 2020 at 1:07 PM Pedro Alves <palves@redhat.com> wrote:
>
> On 2/27/20 4:46 PM, Andrew Burgess wrote:
> > Use std::abs so that we get the C++ overloaded version that matches
> > the argument type instead of the C abs function which is only for int
> > arguments.
>
> Note that stdlib.h/stdmath.h are supposed to provide the overloads in
> the global namespace as well; the standard requires it.  Older
> GCCs got that wrong (e.g. 4.8), but more modern GCCs get it right.
>
> Just a FYI, the patch is fine.

Hm... I saw a build error from this on arm-netbsd with clang 9, I
wonder what happened there. Anyway, the patch does fix it.

Christian

>
> >
> > There should be no user visible change after this commit.
> >
> > gdb/ChangeLog:
> >
> >       * gdbtypes.c (create_array_type_with_stride): Use std::abs not
> >       abs.
>
> Thanks,
> Pedro Alves
>


  reply	other threads:[~2020-02-27 19:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200227164651.13723-1-andrew.burgess@embecosm.com>
2020-02-27 19:06 ` Pedro Alves
2020-02-27 19:09   ` Christian Biesinger via gdb-patches [this message]
2020-02-27 19:26     ` Pedro Alves
2020-02-27 21:10   ` Andrew Burgess

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='CAPTJ0XEz98WLdGw3=OHREEqg4HkLfs6CjVBFFYqxgbC3yGsL=w@mail.gmail.com' \
    --to=gdb-patches@sourceware.org \
    --cc=andrew.burgess@embecosm.com \
    --cc=cbiesinger@google.com \
    --cc=palves@redhat.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