Jason Merrill writes:
> On 10/18/24 11:21 AM, Patrick Palka wrote:
>> On Fri, 18 Oct 2024, Jason Merrill wrote:
>>>
>>> Is it useful for std.cc to live in a subdirectory of c++23 as in this
>>> patch, or
>>> should it be in c++23 itself? Or elsewhere?
>> IIUC the src/ subdirectory is for stuff
On 15/11/24 11:43 -0500, Jason Merrill wrote:
On 11/15/24 10:21 AM, Jonathan Wakely wrote:
On Fri, 15 Nov 2024 at 15:20, Jonathan Wakely wrote:
On Fri, 15 Nov 2024 at 15:12, Jason Merrill wrote:
On 11/15/24 9:20 AM, Jonathan Wakely wrote:
On 15/11/24 08:53 -0500, Jason Merrill wrote:
On
On Fri, 15 Nov 2024 at 15:20, Jonathan Wakely wrote:
>
> On Fri, 15 Nov 2024 at 15:12, Jason Merrill wrote:
> >
> > On 11/15/24 9:20 AM, Jonathan Wakely wrote:
> > > On 15/11/24 08:53 -0500, Jason Merrill wrote:
> > >> On 11/15/24 6:04 AM, Jonathan Wakely wrote:
> > >>> On 14/11/24 23:09 -0500, J
On Fri, 15 Nov 2024 at 15:12, Jason Merrill wrote:
>
> On 11/15/24 9:20 AM, Jonathan Wakely wrote:
> > On 15/11/24 08:53 -0500, Jason Merrill wrote:
> >> On 11/15/24 6:04 AM, Jonathan Wakely wrote:
> >>> On 14/11/24 23:09 -0500, Jason Merrill wrote:
>
> Since bits/stdc++.h also intends to inc
On 11/15/24 9:20 AM, Jonathan Wakely wrote:
On 15/11/24 08:53 -0500, Jason Merrill wrote:
On 11/15/24 6:04 AM, Jonathan Wakely wrote:
On 14/11/24 23:09 -0500, Jason Merrill wrote:
Since bits/stdc++.h also intends to include the whole standard
library, I
include it rather than duplicate it.
On 15/11/24 08:53 -0500, Jason Merrill wrote:
On 11/15/24 6:04 AM, Jonathan Wakely wrote:
On 14/11/24 23:09 -0500, Jason Merrill wrote:
On 10/18/24 9:38 AM, Jason Merrill wrote:
Currently this installs the sources under $(gxx_include_dir)/bits/,
i.e. /usr/include/c++/15/bits. So with my -fs
On 11/15/24 6:04 AM, Jonathan Wakely wrote:
On 14/11/24 23:09 -0500, Jason Merrill wrote:
On 10/18/24 9:38 AM, Jason Merrill wrote:
Currently this installs the sources under $(gxx_include_dir)/bits/,
i.e. /usr/include/c++/15/bits. So with my -fsearch-include-path change,
std.cc can be compil
On 14/11/24 23:09 -0500, Jason Merrill wrote:
On 10/18/24 9:38 AM, Jason Merrill wrote:
This patch is not ready for integration, but I'd like to get feedback on the
approach (and various specific questions below).
An updated version:
From 533c496ae39ba2cf1783136e1da5ae9f0f61d4f7 Mon Sep 17
On Tue, 22 Oct 2024 at 15:03, Jason Merrill wrote:
>
> On 10/22/24 4:26 AM, Jonathan Wakely wrote:
> > On Mon, 21 Oct 2024 at 17:51, Jason Merrill wrote:
> >>
> >> On 10/18/24 11:21 AM, Patrick Palka wrote:
> >>> On Fri, 18 Oct 2024, Jason Merrill wrote:
>
> Is it useful for std.cc to l
On 10/22/24 4:26 AM, Jonathan Wakely wrote:
On Mon, 21 Oct 2024 at 17:51, Jason Merrill wrote:
On 10/18/24 11:21 AM, Patrick Palka wrote:
On Fri, 18 Oct 2024, Jason Merrill wrote:
Is it useful for std.cc to live in a subdirectory of c++23 as in this patch, or
should it be in c++23 itself?
On Mon, 21 Oct 2024 at 17:51, Jason Merrill wrote:
>
> On 10/18/24 11:21 AM, Patrick Palka wrote:
> > On Fri, 18 Oct 2024, Jason Merrill wrote:
> >>
> >> Is it useful for std.cc to live in a subdirectory of c++23 as in this
> >> patch, or
> >> should it be in c++23 itself? Or elsewhere?
> >
> >
On 10/18/24 11:21 AM, Patrick Palka wrote:
On Fri, 18 Oct 2024, Jason Merrill wrote:
Is it useful for std.cc to live in a subdirectory of c++23 as in this patch, or
should it be in c++23 itself? Or elsewhere?
IIUC the src/ subdirectory is for stuff that gets compiled into the .so
which isn't
* Jason Merrill:
> This patch is not ready for integration, but I'd like to get feedback on the
> approach (and various specific questions below).
>
> -- 8< --
>
> This patch introduces an installed source form of module std and std.compat.
> To find them, we install a libstdc++.modules.json file
> On 18 Oct 2024, at 14:38, Jason Merrill wrote:
>
> This patch is not ready for integration, but I'd like to get feedback on the
> approach (and various specific questions below).
>
> -- 8< --
>
> This patch introduces an installed source form of module std and std.compat.
> To find them, w
Hi,
Thanks for working on this!
> stdc++.h also doesn't include the eternally deprecated . There
are some other deprecated facilities that I notice are included:
and float_denorm_style, at least. It would be nice for L{E,}WG to clarify
whether module std is intended to include interfaces that
On Fri, 18 Oct 2024, Jason Merrill wrote:
> This patch is not ready for integration, but I'd like to get feedback on the
> approach (and various specific questions below).
>
> -- 8< --
>
> This patch introduces an installed source form of module std and std.compat.
> To find them, we install a l
16 matches
Mail list logo
