public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jakub Jelinek <jakub@redhat.com>
To: JeanHeyd Meneide <phdofthehouse@gmail.com>
Cc: gcc-patches@gcc.gnu.org, libstdc++ <libstdc++@gcc.gnu.org>,
	       Jonathan Wakely <jwakely@redhat.com>
Subject: Re: [ PATCH ] [ C++ ] [ libstdc++ ] P1208r6 Merge source_location
Date: Fri, 27 Dec 2019 19:33:00 -0000	[thread overview]
Message-ID: <20191227193329.GM10088@tucnak> (raw)
In-Reply-To: <CANHA4Oiog-fEJszB+kf4WbTux5WtFfbZ4OpWUxdJhGBoPV=BEQ@mail.gmail.com>

On Fri, Dec 27, 2019 at 02:27:12PM -0500, JeanHeyd Meneide wrote:
>      This patch implements std::source_location. There's a couple
> cases where the builtin implemented does not do what is expected of
> it, and so the bottom 3 batches of test cases fails. I'm still
> including the patch so that others can pick up on what might need to
> change about the __builtin_source_location implementation (CC:
> Jonathan Wakely, Jakub Jelinek).
> 
> 2019-12-27  JeanHeyd "ThePhD" Meneide  <phdofthehouse@gmail.com>
> 
>         * include/Makefile.in: add source_location header
>         * include/bits/c++config: Add new detection macros for
>           LINE, COLUMN, and SOURCE_LOCATION builtins.
>         * include/std/source_location: New.
>         * testuite/std/support/srcloc/std.n4842.C (new): test source_location
>         * testuite/std/support/srcloc/std.n4842.h (new): test source_location

This will be ABI incompatible between GCC and Clang, that doesn't look like
a good idea to me.  I thought the plan is to use what you have in the
_GLIBCXX_HAVE_BUILTIN_SOURCE_LOCATION case always, except that if
__builtin_source_location isn't available, initialize _M_data to nullptr.

	Jakub

  reply	other threads:[~2019-12-27 19:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-27 19:27 JeanHeyd Meneide
2019-12-27 19:33 ` Jakub Jelinek [this message]
2019-12-28  3:28   ` JeanHeyd Meneide
2020-01-02 10:28     ` Jonathan Wakely
2020-01-02 21:57       ` JeanHeyd Meneide
2020-01-02 22:07         ` Jakub Jelinek
2020-01-02 22:21           ` JeanHeyd Meneide
2020-12-03 19:25             ` Jonathan Wakely

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=20191227193329.GM10088@tucnak \
    --to=jakub@redhat.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@gcc.gnu.org \
    --cc=phdofthehouse@gmail.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).