Importable STL Header Units?

2022-07-25 Thread Zopolis0 via Gcc
Currently, when importing the standard library, one has to separately compile each unit they want to use, which is a hindrance to the build process and a gap in the implementation. Is there any particular reason why gcc doesn't provide importable header units for the standard library? Is there a t

Re: Importable STL Header Units?

2022-07-25 Thread Ben Boeckel via Gcc
On Mon, Jul 25, 2022 at 19:48:28 +1000, Zopolis0 via Gcc wrote: > Currently, when importing the standard library, one has to > separately compile each unit they want to use, which is a hindrance to the > build process and a gap in the implementation. > > Is there any particular reason why gcc does

Re: Importable STL Header Units?

2022-07-25 Thread Jonathan Wakely via Gcc
On Mon, 25 Jul 2022 at 10:49, Zopolis0 via Gcc wrote: > > Currently, when importing the standard library, one has to > separately compile each unit they want to use, which is a hindrance to the > build process and a gap in the implementation. > > Is there any particular reason why gcc doesn't prov

Re: libiberty D tuple demangling

2022-07-25 Thread ibuclaw--- via Gcc
> On 25/07/2022 08:45 CEST Jan Beulich wrote: > > > Hello, > > while commit 3f30a274913b ("libiberty: Update D symbol demangling > for latest ABI spec") mentions in its description that tuple encoding > has changed, there's no real adjustment to dlang_parse_tuple() there, > nor are there any n

Re: libiberty D tuple demangling

2022-07-25 Thread Jan Beulich via Gcc
On 25.07.2022 14:05, ibuc...@gdcproject.org wrote: >> On 25/07/2022 08:45 CEST Jan Beulich wrote: >> while commit 3f30a274913b ("libiberty: Update D symbol demangling >> for latest ABI spec") mentions in its description that tuple encoding >> has changed, there's no real adjustment to dlang_parse_

Re: [RFC] Function Multi Versioning on Arm

2022-07-25 Thread Martin Liška
On 7/22/22 10:40, Daniel Kiss wrote: > IMHO it would make sense if the “default" attribute becomes optional for > “target”. I'm not against it, but it can be done incrementally. Cheers, Martin

Re: libiberty D tuple demangling

2022-07-25 Thread ibuclaw--- via Gcc
> On 25/07/2022 14:13 CEST Jan Beulich wrote: > > > On 25.07.2022 14:05, ibuc...@gdcproject.org wrote: > >> On 25/07/2022 08:45 CEST Jan Beulich wrote: > >> while commit 3f30a274913b ("libiberty: Update D symbol demangling > >> for latest ABI spec") mentions in its description that tuple encod

Re: libiberty D tuple demangling

2022-07-25 Thread Jan Beulich via Gcc
On 25.07.2022 17:45, ibuc...@gdcproject.org wrote: >> On 25/07/2022 14:13 CEST Jan Beulich wrote: >> >> >> On 25.07.2022 14:05, ibuc...@gdcproject.org wrote: On 25/07/2022 08:45 CEST Jan Beulich wrote: while commit 3f30a274913b ("libiberty: Update D symbol demangling for latest A

How to best reference ltdl.m4?

2022-07-25 Thread Zopolis0 via Gcc
As part of my gcj work, I need to call a couple of variables and functions from ltdl.m4 (installed in usr/share/aclocal, as part of libltdl). Should I reference the system installed copy? How would I do that? Or should I copy it into the gcc root directory, like what was done with libtool.m4? If