From: Pedro Alves <palves@redhat.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2 3/5] Add gdb::string_view
Date: Fri, 06 Apr 2018 22:01:00 -0000 [thread overview]
Message-ID: <559112fa-ecd7-028c-18f5-fb8a1f0575a2@redhat.com> (raw)
In-Reply-To: <7a85c51e05bada7f80daf413c0dd0e6c@polymtl.ca>
On 04/06/2018 09:37 PM, Simon Marchi wrote:
> Ah, from the name I thought that experimental version contained the code implementing future standards, before they were official... so I'll start from scratch using the version from experimental, does that sounds good?
It does. However, there may have been other enhancements, small API changes, and
bugfixes to string_view when it was merged to the standard proper (and subsequent
DRs), so I'd still recommend perusing the diff a bit. Though if the tests still
pass, it'll likely the differences won't matter much.
>>> Â Â template<>
>>> Â Â Â Â struct hash<string_view>
>>> -Â Â Â : public __hash_base<size_t, string_view>
>>> +Â Â Â : public std::__hash_base<size_t, string_view>
>>
>> This looks suspiciously like using an internal implementation
>> detail of libstdc++. Where is std::__hash_base defined?
>> Does this compile with clang + libc++ ?
>
> Hmm indeed. Well, it looks like building with clang + libstdcxx fails. I'll make sure to test both of these combinations in the next iteration.
Thanks.
Pedro Alves
next prev parent reply other threads:[~2018-04-06 22:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-30 21:47 [PATCH v2 1/5] Update ax_cv_cxx_compile_cxx.m4 Simon Marchi
2018-03-30 21:47 ` [PATCH v2 5/5] Adapt and integrate string_view tests Simon Marchi
2018-04-06 18:20 ` Pedro Alves
2018-03-30 21:47 ` [PATCH v2 3/5] Add gdb::string_view Simon Marchi
2018-04-06 18:08 ` Pedro Alves
2018-04-06 20:37 ` Simon Marchi
2018-04-06 22:01 ` Pedro Alves [this message]
2018-03-30 21:47 ` [PATCH v2 2/5] Copy string_view files from libstdc++ Simon Marchi
2018-03-30 21:47 ` [PATCH v2 4/5] Copy string_view tests " 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=559112fa-ecd7-028c-18f5-fb8a1f0575a2@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@polymtl.ca \
/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