Hi,
instead of uglyfing all the libstdc++ code wouldn't it be simpler to
just ignore all non-reserved macro expansions (+ some special ones
like assert) inside system headers on compiler level?
Regards,
Maciej
On Thu, 16 Feb 2023 at 11:45, Jakub Jelinek wrote:
>
> On Thu, Feb 16, 2023 at 11:47:54AM +0100, Jakub Jelinek via Gcc-patches wrote:
> > On Thu, Feb 16, 2023 at 10:30:30AM +, Jonathan Wakely via Gcc-patches
> > wrote:
> > > Tested powerpc64le-linux. Pushed to trunk.
> > >
> > > These should
On Thu, 16 Feb 2023 at 10:48, Jakub Jelinek wrote:
>
> On Thu, Feb 16, 2023 at 10:30:30AM +, Jonathan Wakely via Gcc-patches
> wrote:
> > Tested powerpc64le-linux. Pushed to trunk.
> >
> > These should be backported too.
> >
> > -- >8 --
> >
> > The non-reserved names 'val' and 'dest' were be
On Thu, Feb 16, 2023 at 11:47:54AM +0100, Jakub Jelinek via Gcc-patches wrote:
> On Thu, Feb 16, 2023 at 10:30:30AM +, Jonathan Wakely via Gcc-patches
> wrote:
> > Tested powerpc64le-linux. Pushed to trunk.
> >
> > These should be backported too.
> >
> > -- >8 --
> >
> > The non-reserved na
On Thu, Feb 16, 2023 at 10:30:30AM +, Jonathan Wakely via Gcc-patches wrote:
> Tested powerpc64le-linux. Pushed to trunk.
>
> These should be backported too.
>
> -- >8 --
>
> The non-reserved names 'val' and 'dest' were being used in our headers
> but haven't been added to the 17_intro/names
Tested powerpc64le-linux. Pushed to trunk.
These should be backported too.
-- >8 --
The non-reserved names 'val' and 'dest' were being used in our headers
but haven't been added to the 17_intro/names.cc test. That's because
they are used by and
respecitvely on glibc-based systems.
libstdc++-v
