[PATCH,doc] install: Drop hppa*-hp-hpux10, remove old notes on hppa*-hp-hpux11

2023-12-16 Thread Gerald Pfeifer
Hi Dave, based on our earlier e-mail, I understand we don't support hppa*-hp-hpux10 any longer, so let's remove them from the installation docs. On the way remove references to GCC 2.95 and 3.0 from hppa*-hp-hpux11. Okay? (I believe it would be great if you could have a look at that part of

Re: [PATCH] install: Streamline the hppa*-hp-hpux* section

2023-12-16 Thread Gerald Pfeifer
On Sat, 16 Dec 2023, John David Anglin wrote: > I have one comment. The only target currently supported is > hppa64-hp-hpux11*. While gas is required, only the HP ld works. > > Otherwise, the change looks fine. Thank you, Dave! I updated the patch accordingly, referring to gas (not

RFC -- targets with unsigned bifields

2023-12-16 Thread Jeff Law
So mcore-elf is the slowest target to test with a simulator. Not because it's simulator is particularly bad, but because some tests timeout as they've gotten into infinite loops. This causes the mcore-elf port to take about 2X longer than most other gdbsim ports. I tracked this down to

Re: [PATCH 2/3] LoongArch: Fix instruction costs [PR112936]

2023-12-16 Thread chenglulu
在 2023/12/15 下午3:56, chenglulu 写道: 在 2023/12/14 上午9:16, chenglulu 写道: 在 2023/12/13 下午9:20, Xi Ruoyao 写道: On Wed, 2023-12-13 at 20:22 +0800, chenglulu wrote: 在 2023/12/10 上午1:03, Xi Ruoyao 写道: Replace the instruction costs in loongarch_rtx_cost_data constructor based on micro-benchmark

Re: [PATCH] install: Streamline the hppa*-hp-hpux* section

2023-12-16 Thread John David Anglin
Hi Gerald, I have one comment.  The only target currently supported is hppa64-hp-hpux11*. While gas is required, only the HP ld works. Otherwise, the change looks fine. Dave On 2023-12-16 8:35 p.m., Gerald Pfeifer wrote: John, Jeff, I suggest to streamline the hppa*-hp-hpux* installation

[PATCH] install: Streamline the hppa*-hp-hpux* section

2023-12-16 Thread Gerald Pfeifer
John, Jeff, I suggest to streamline the hppa*-hp-hpux* installation instructions as follows. Okay? In fact in the following sections there is even more, and more specific material, which would be great could you have a look at and help trim. Gerald >From

[pushed] doc: Remove references to buildstat.html

2023-12-16 Thread Gerald Pfeifer
After addressing the references to the stale information Thomas pointed out on our web pages, this addresses our documentation. (I can't believe we still had a reference to SuSE, more than twenty years after the name changed to SUSE.) Gerald gcc: PR other/69374 *

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread David Edelsohn
On Sat, Dec 16, 2023 at 7:04 PM Jonathan Wakely wrote: > On Sun, 17 Dec 2023 at 00:02, Jonathan Wakely wrote: > > > > On Sat, 16 Dec 2023 at 23:06, David Edelsohn wrote: > > > > > > On Sat, Dec 16, 2023 at 4:44 PM Jakub Jelinek > wrote: > > >> > > >> On Sat, Dec 16, 2023 at 04:24:13PM -0500,

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread Jonathan Wakely
On Sun, 17 Dec 2023 at 00:02, Jonathan Wakely wrote: > > On Sat, 16 Dec 2023 at 23:06, David Edelsohn wrote: > > > > On Sat, Dec 16, 2023 at 4:44 PM Jakub Jelinek wrote: > >> > >> On Sat, Dec 16, 2023 at 04:24:13PM -0500, David Edelsohn wrote: > >> > AIX stdio.h defines fileno as a macro

[committed] libstdc++: Fix bootstrap on AIX due to fileno macro

2023-12-16 Thread Jonathan Wakely
Tested x86_64-linux (and built on AIX). Pushed to trunk. -- >8 -- On AIX fileno is a function-like macro, so enclose the name in parentheses to ensure we use the real function. libstdc++-v3/ChangeLog: * src/c++23/print.cc (__open_terminal(FILE*)): Avoid fileno macro. ---

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread Jonathan Wakely
On Sat, 16 Dec 2023 at 23:06, David Edelsohn wrote: > > On Sat, Dec 16, 2023 at 4:44 PM Jakub Jelinek wrote: >> >> On Sat, Dec 16, 2023 at 04:24:13PM -0500, David Edelsohn wrote: >> > AIX stdio.h defines fileno as a macro although there is a symbol in libc. >> > >> > I think that print.cc at

Re: [PATCH] c++/modules: seed namespaces for bindings [PR106363]

2023-12-16 Thread Nathan Sidwell
On 12/16/23 05:31, Nathaniel Shead wrote: Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636159.html ok On Sun, Nov 12, 2023 at 12:59:36PM +1100, Nathaniel Shead wrote: Bootstrapped and regtested on x86_64-pc-linux-gnu. I don't have write access. -- >8 -- Currently the

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread David Edelsohn
On Sat, Dec 16, 2023 at 4:44 PM Jakub Jelinek wrote: > On Sat, Dec 16, 2023 at 04:24:13PM -0500, David Edelsohn wrote: > > AIX stdio.h defines fileno as a macro although there is a symbol in libc. > > > > I think that print.cc at least needs to > > > > > > #undef fileno > > > > > > before the

[wwwdocs] Update notes on libstdc++ header dependency changes in GCC 14

2023-12-16 Thread Jonathan Wakely
Pushed to wwwdocs. -- >8 -- --- htdocs/gcc-14/porting_to.html | 6 +- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/htdocs/gcc-14/porting_to.html b/htdocs/gcc-14/porting_to.html index dea9ac80..3e4cedc3 100644 --- a/htdocs/gcc-14/porting_to.html +++

[wwwdocs] Document std::print and std::ranges::to for C++23

2023-12-16 Thread Jonathan Wakely
Pushed to wwwdocs. -- >8 -- --- htdocs/gcc-14/changes.html | 12 +--- 1 file changed, 9 insertions(+), 3 deletions(-) diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html index 346785a0..eb14e09d 100644 --- a/htdocs/gcc-14/changes.html +++ b/htdocs/gcc-14/changes.html

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread Jakub Jelinek
On Sat, Dec 16, 2023 at 04:24:13PM -0500, David Edelsohn wrote: > AIX stdio.h defines fileno as a macro although there is a symbol in libc. > > I think that print.cc at least needs to > > > #undef fileno > > > before the usage. Or (::fileno)(f) ? Jakub

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread David Edelsohn
Hi, Jonathan Unfortunately this patch broke bootstrap on AIX. In file included from /tmp/GCC/gcc/include-fixed/wchar.h:64, from /tmp/GCC/powerpc-ibm-aix7.2.5.0/libstdc++-v3/include/cwchar:44, from

[pushed] analyzer: add sarif properties for bounds checking diagnostics

2023-12-16 Thread David Malcolm
As a followup to r14-6057-g12b67d1e13b3cf, add SARIF property bags for -Wanalyzer-out-of-bounds, to help with debugging these warnings. This was very helpful with PR analyzer/112792. Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Successful run of analyzer integration tests on

[pushed] json: fix escaping of object keys

2023-12-16 Thread David Malcolm
Successfully bootstrapped & regrtested on x86_64-pc-linux-gnu. Successful run of analyzer integration tests on x86_64-pc-linux-gnu. Pushed to trunk as r14-6634-g30d9a3a69841b1. gcc/ChangeLog: * json.cc (print_escaped_json_string): New, taken from string::print.

[PATCH] PR libstdc++/112682 More efficient std::basic_string move

2023-12-16 Thread Antony Polukhin
A few places in bits/basic_string.h use `traits_type::copy` to copy `__str.length() + 1` bytes. Despite the knowledge that `__str.length()` is not greater than 15 the compiler emits (and sometimes inlines) a `memcpy` call. That results in a quite big set of instructions

Re: [PATCH] RISC-V: Don't make Ztso imply A

2023-12-16 Thread Jeff Law
On 12/15/23 17:14, Andrew Waterman wrote: On Fri, Dec 15, 2023 at 1:38 PM Jeff Law wrote: On 12/12/23 20:54, Palmer Dabbelt wrote: I can't actually find anything in the ISA manual that makes Ztso imply A. In theory the memory ordering is just a different thing that the set of

[PATCH] libstdc++: Update some baseline_symbols.txt (x32)

2023-12-16 Thread H.J. Lu
* config/abi/post/x86_64-linux-gnu/x32/baseline_symbols.txt: Updated. --- .../x86_64-linux-gnu/x32/baseline_symbols.txt | 111 +- 1 file changed, 110 insertions(+), 1 deletion(-) diff --git a/libstdc++-v3/config/abi/post/x86_64-linux-gnu/x32/baseline_symbols.txt

[PATCH] Fortran: fix argument passing to CONTIGUOUS,TARGET dummy [PR97592]

2023-12-16 Thread Harald Anlauf
Dear all, the attached simple patch fixes a (9+) regression for passing to a CONTIGUOUS,TARGET dummy an *effective argument* that is contiguous, although the actual argument is not simply-contiguous (it is a pointer without the CONTIGOUS attribute in the PR). Since a previous attempt for a patch

Re: [PATCH v26 00/23] Optimize type traits compilation performance

2023-12-16 Thread Ken Matsui
On Sat, Dec 16, 2023 at 8:40 AM Jonathan Wakely wrote: > > On Sun, 10 Dec 2023 at 18:19, Jason Merrill wrote: > > > > On 12/7/23 00:11, Ken Matsui wrote: > > > This patch series optimizes type traits compilation performance by > > > implementing built-in type traits and using them in libstdc++. >

Re: [PATCH] x86: Get the previous shadow stack pointer from the restore token

2023-12-16 Thread H.J. Lu
On Sat, Dec 16, 2023 at 8:41 AM Richard Biener wrote: > > > > > Am 16.12.2023 um 16:56 schrieb H.J. Lu : > > > > Linux CET kernel places a restore token on shadow stack followed by > > optional additional information for signal handler to enhance security. > > The restore token is the previous

Re: [PATCH] x86: Get the previous shadow stack pointer from the restore token

2023-12-16 Thread Richard Biener
> Am 16.12.2023 um 16:56 schrieb H.J. Lu : > > Linux CET kernel places a restore token on shadow stack followed by > optional additional information for signal handler to enhance security. > The restore token is the previous shadow stack pointer with bit 63 set. > It is usually transparent to

Re: [PATCH v26 00/23] Optimize type traits compilation performance

2023-12-16 Thread Jonathan Wakely
On Sun, 10 Dec 2023 at 18:19, Jason Merrill wrote: > > On 12/7/23 00:11, Ken Matsui wrote: > > This patch series optimizes type traits compilation performance by > > implementing built-in type traits and using them in libstdc++. > > > > Changes in v26: > > > > * Rebased on top of trunk. > >

Re: [PATCH] libstdc++: Make __gnu_debug::vector usable in constant expressions [PR109536]

2023-12-16 Thread Jonathan Wakely
On Sat, 16 Dec 2023 at 16:26, Patrick Palka wrote: > > On Sat, 16 Dec 2023, Jonathan Wakely wrote: > > > On Sat, 16 Dec 2023 at 09:14, Jonathan Wakely wrote: > > > > > > On Sat, 16 Dec 2023 at 00:27, Patrick Palka wrote: > > > > > > > > On Wed, 6 Dec 2023, Jonathan Wakely wrote: > > > > > > > > >

Re: [PATCH] libstdc++: Make __gnu_debug::vector usable in constant expressions [PR109536]

2023-12-16 Thread Patrick Palka
On Sat, 16 Dec 2023, Jonathan Wakely wrote: > On Sat, 16 Dec 2023 at 09:14, Jonathan Wakely wrote: > > > > On Sat, 16 Dec 2023 at 00:27, Patrick Palka wrote: > > > > > > On Wed, 6 Dec 2023, Jonathan Wakely wrote: > > > > > > > Any comments on this approach? > > > > > > > > -- >8 -- > > > > > > >

[PATCH] x86: Get the previous shadow stack pointer from the restore token

2023-12-16 Thread H.J. Lu
Linux CET kernel places a restore token on shadow stack followed by optional additional information for signal handler to enhance security. The restore token is the previous shadow stack pointer with bit 63 set. It is usually transparent to user programs since kernel will pop the restore token and

[pushed] analyzer: use bit-level granularity for concrete bounds-checking [PR112792]

2023-12-16 Thread David Malcolm
PR analyzer/112792 reports false positives from -fanalyzer's bounds-checking on certain packed structs containing bitfields e.g. in the Linux kernel's drivers/dma/idxd/device.c: union msix_perm { struct { u32 rsvd2 : 8; u32 pasid : 20; }; u32 bits; } __attribute__((__packed__));

Re: [PATCH v7 5/5] OpenMP/OpenACC: Reorganise OMP map clause handling in gimplify.cc

2023-12-16 Thread Julian Brown
On Fri, 18 Aug 2023 15:47:51 -0700 Julian Brown wrote: > This patch has been separated out from the C++ "declare mapper" > support patch. It contains just the gimplify.cc rearrangement > work, mostly moving gimplification from gimplify_scan_omp_clauses > to gimplify_adjust_omp_clauses for map

[PATCH v2] c++: Follow module grammar more closely [PR110808]

2023-12-16 Thread Nathaniel Shead
Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-November/638089.html On Fri, Nov 24, 2023 at 10:32:13PM +1100, Nathaniel Shead wrote: > On Thu, Nov 23, 2023 at 12:11:58PM -0500, Nathan Sidwell wrote: > > On 11/14/23 01:24, Nathaniel Shead wrote: > > > I'll also note that the comments

[PATCH] c++/modules: Prevent overwriting arguments when merging duplicates [PR112588]

2023-12-16 Thread Nathaniel Shead
Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-November/637768.html. (I've changed the summary message a little from that email but the patch is otherwise unchanged.) On Wed, Nov 22, 2023 at 10:33:15PM +1100, Nathaniel Shead wrote: > Bootstrapped and regtested on x86_64-pc-linux-gnu. I

Re: [PATCH] c++/modules: seed namespaces for bindings [PR106363]

2023-12-16 Thread Nathaniel Shead
Ping for https://gcc.gnu.org/pipermail/gcc-patches/2023-November/636159.html On Sun, Nov 12, 2023 at 12:59:36PM +1100, Nathaniel Shead wrote: > Bootstrapped and regtested on x86_64-pc-linux-gnu. I don't have write > access. > > -- >8 -- > > Currently the first depset for an EK_BINDING is not

Re: [PATCH] libstdc++: Make __gnu_debug::vector usable in constant expressions [PR109536]

2023-12-16 Thread Jonathan Wakely
On Sat, 16 Dec 2023 at 09:14, Jonathan Wakely wrote: > > On Sat, 16 Dec 2023 at 00:27, Patrick Palka wrote: > > > > On Wed, 6 Dec 2023, Jonathan Wakely wrote: > > > > > Any comments on this approach? > > > > > > -- >8 -- > > > > > > This makes constexpr std::vector (mostly) work in Debug Mode. All

Re: [PATCH] libstdc++: Make __gnu_debug::vector usable in constant expressions [PR109536]

2023-12-16 Thread Jonathan Wakely
On Sat, 16 Dec 2023 at 00:27, Patrick Palka wrote: > > On Wed, 6 Dec 2023, Jonathan Wakely wrote: > > > Any comments on this approach? > > > > -- >8 -- > > > > This makes constexpr std::vector (mostly) work in Debug Mode. All safe > > iterator instrumentation and checking is disabled during

Re: [committed] libstdc++: Implement C++23 header [PR107760]

2023-12-16 Thread Jonathan Wakely
On Fri, 15 Dec 2023 at 14:49, Tim Song wrote: > > > > On Fri, Dec 15, 2023 at 4:43 AM Jonathan Wakely wrote: >> >> On Fri, 15 Dec 2023 at 01:17, Tim Song wrote: >> > >> > On Thu, Dec 14, 2023 at 6:05 PM Jonathan Wakely wrote: >> >> + inline void >> >> + vprint_unicode(ostream& __os,

Re: [PATCH] Add type-generic clz/ctz/clrsb/ffs/parity/popcount builtins [PR111309]

2023-12-16 Thread Jakub Jelinek
On Fri, Dec 15, 2023 at 09:51:10PM -0800, Andrew Pinski wrote: > I was looking into improving __builtin_popcountg for __int128 on > aarch64 (when CSSC is not implemented which right now is almost all > cores) but this patch forces __builtin_popcountg to expand into 2 > __builtin_popcountll (and