From: Tom Tromey <tom@tromey.com>
To: Simon Marchi <simark@simark.ca>
Cc: Tom Tromey <tom@tromey.com>,
Simon Marchi <simon.marchi@ericsson.com>,
gdb-patches@sourceware.org
Subject: Re: [RFA] Make macOS build warning-free
Date: Tue, 03 Jul 2018 13:17:00 -0000 [thread overview]
Message-ID: <87k1qco3vk.fsf@tromey.com> (raw)
In-Reply-To: <5f9b4ce1-aa8d-30e3-98f9-f2c36c3869c6@simark.ca> (Simon Marchi's message of "Mon, 2 Jul 2018 12:53:09 -0400")
>>>>> "Simon" == Simon Marchi <simark@simark.ca> writes:
Simon> _INTL_MAY_RETURN_STRING_ARG thing is a gcc/binutils/gdb addition, on top of the
Simon> v0.12.1 version of gettext. So we shouldn't have to deal with upstream gettext
Simon> to fix this, since it's just the gcc/binutils/gdb addition that needs to be fixed.
It's upstream as well though. Maybe it was upstreamed from gcc to
gettext? I don't really know the history there.
I'll send a note to the gettext list.
Simon> That bit looks good to me, at least to shut up the compiler. But I'm wondering
Simon> if we still need that section_offsets structure, or if we could just replace
Simon> it with std::vector<CORE_ADDR>/gdb:array_view<CORE_ADDR>.
I think it's a good idea to rewrite section_offsets, but that seems more involved.
Also the way that this code is using std::vector and then turning it
into a section_offsets* seems incorrect.
I think the symfile.c change isn't enough, btw; the
-Wno-deprecated-declarations bit is also required. Otherwise there is at
least one error (about the use of syscall). But maybe I could disable that
one with a #pragma instead - what do you think?
Tom
next prev parent reply other threads:[~2018-07-03 13:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-29 16:55 Tom Tromey
2018-06-29 21:34 ` Simon Marchi
2018-07-02 14:58 ` Tom Tromey
2018-07-02 16:53 ` Simon Marchi
2018-07-03 13:17 ` Tom Tromey [this message]
2018-07-03 15:58 ` Simon Marchi
2018-07-03 17:43 ` Tom Tromey
2018-07-13 17:16 ` Tom Tromey
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=87k1qco3vk.fsf@tromey.com \
--to=tom@tromey.com \
--cc=gdb-patches@sourceware.org \
--cc=simark@simark.ca \
--cc=simon.marchi@ericsson.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).