From: Lukas Durfina <ldurfina@tachyum.com>
To: "Aktemur, Tankut Baris" <tankut.baris.aktemur@intel.com>,
Simon Marchi <simark@simark.ca>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: RE: [PATCH 2/2] gdb: Fix a type of sentinel
Date: Thu, 30 Jan 2020 14:52:00 -0000 [thread overview]
Message-ID: <f7eb5ad5bde84107a7dc243ad4bad8b9@tachyum.com> (raw)
In-Reply-To: <BYAPR11MB3030F52EC57DD75DAEB5AB7AC40A0@BYAPR11MB3030.namprd11.prod.outlook.com>
Hello,
nullptr works of course too. I will prepare the second version with nullptr.
To Simon: I will merge both patches into the single one.
Also, I will update the commit message about fixed compilation error.
You are right, it fixes the issue for cross compiling, but for our new architecture (Tachyum) that is being developed.
I assume the change is generic improvement.
Thanks
Lukas
> -----Original Message-----
> From: Aktemur, Tankut Baris <tankut.baris.aktemur@intel.com>
> Sent: Tuesday, January 28, 2020 6:06 PM
> To: Simon Marchi <simark@simark.ca>; Lukas Durfina
> <ldurfina@tachyum.com>; gdb-patches@sourceware.org
> Subject: RE: [PATCH 2/2] gdb: Fix a type of sentinel
>
> On Tuesday, January 28, 2020 5:44 PM, Simon Marchi wrote:
> > On 2020-01-28 9:28 a.m., Lukas Durfina wrote:
> > > ---
> > > gdb/ChangeLog | 4 ++++
> > > gdb/charset.c | 2 +-
> > > 2 files changed, 5 insertions(+), 1 deletion(-)
> > >
> > > diff --git a/gdb/ChangeLog b/gdb/ChangeLog index
> > > 8b6da62bd4..1dd89ae2e0 100644
> > > --- a/gdb/ChangeLog
> > > +++ b/gdb/ChangeLog
> > > @@ -1,3 +1,7 @@
> > > +2020-01-28 Lukas Durfina <ldurfina@tachyum.com>
> > > +
> > > + * charset.c (find_charset_names): Fix a type of sentinel.
> > > +
> > > 2020-01-26 Tom Tromey <tom@tromey.com>
> > >
> > > * ctfread.c (struct ctf_fp_info): Reindent.
> > > diff --git a/gdb/charset.c b/gdb/charset.c index
> > > 5cfd2d8030..abf795ce6d 100644
> > > --- a/gdb/charset.c
> > > +++ b/gdb/charset.c
> > > @@ -818,7 +818,7 @@ find_charset_names (void)
> > > {
> > > std::string iconv_dir = relocate_gdb_directory (ICONV_BIN,
> > >
> ICONV_BIN_RELOCATABLE);
> > > - iconv_program = concat (iconv_dir.c_str(), SLASH_STRING, "iconv",
> NULL);
> > > + iconv_program = concat (iconv_dir.c_str(), SLASH_STRING,
> > > + "iconv", (char *) NULL);
> > > }
> > > #else
> > > iconv_program = xstrdup ("iconv");
> > > --
> > > 2.17.1
> > >
> >
> > Hi Lukas,
> >
> > Same comment as patch 1/2.
> >
> > If this change fixes the same problem as patch 1/2, then you can put
> > both changes in the same patch.
> >
> > Simon
>
> Now that the line is being touched, it might also be a good idea to replace
> NULL with nullptr.
>
> -Baris
>
>
> Intel Deutschland GmbH
> Registered Address: Am Campeon 10-12, 85579 Neubiberg, Germany
> Tel: +49 89 99 8853-0, www.intel.de
> Managing Directors: Christin Eisenschmid, Gary Kershaw Chairperson of the
> Supervisory Board: Nicole Lau Registered Office: Munich Commercial
> Register: Amtsgericht Muenchen HRB 186928
next prev parent reply other threads:[~2020-01-30 13:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 14:28 [PATCH 1/2] gdbsupport: " Lukas Durfina
2020-01-28 15:05 ` [PATCH 2/2] gdb: " Lukas Durfina
2020-01-28 16:53 ` Simon Marchi
2020-01-28 17:13 ` Aktemur, Tankut Baris
2020-01-30 14:52 ` Lukas Durfina [this message]
2020-01-28 16:44 ` [PATCH 1/2] gdbsupport: " Simon Marchi
2020-01-31 10:09 ` Tom Tromey
2020-01-31 18:37 ` Simon Marchi
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=f7eb5ad5bde84107a7dc243ad4bad8b9@tachyum.com \
--to=ldurfina@tachyum.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=tankut.baris.aktemur@intel.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