Re: [PATCH] [libstdc++] add _GLIBCXX_CLANG to workaround predefined __clang__

2024-06-01 Thread Olivier Hainque
> On 31 May 2024, at 17:52, Alexandre Oliva wrote: >> Does the vxworks toolchain need to support the PSTL headers? > > Maybe we can do without them. I really don't know. Olivier? I have no indication that we can not-support these. We are seeing many cases of C++/Ada combined codebases in

[PATCH v2] RISC-V: Add Zfbfmin extension

2024-06-01 Thread Xiao Zeng
1 In the previous patch, the libcall for BF16 was implemented: 2 Riscv provides Zfbfmin extension, which completes the "Scalar BF16 Converts":

Re: Re: [PING] [PATCH] RISC-V: Add Zfbfmin extension

2024-06-01 Thread Xiao Zeng
2024-06-01 12:34  Jeff Law wrote: > > > >On 5/30/24 5:38 AM, Xiao Zeng wrote: >> 1 In the previous patch, the libcall for BF16 was implemented: >> >> >> 2 Riscv provides Zfbfmin extension, which completes the

Re: [PATCH] [libstdc++] add _GLIBCXX_CLANG to workaround predefined __clang__

2024-06-01 Thread Jonathan Wakely
On Sat, 1 Jun 2024 at 08:35, Olivier Hainque wrote: > > > > > On 31 May 2024, at 17:52, Alexandre Oliva wrote: > > >> Does the vxworks toolchain need to support the PSTL headers? > > > > Maybe we can do without them. I really don't know. Olivier? > > I have no indication that we can not-support

Re: [PATCH] [libstdc++] add _GLIBCXX_CLANG to workaround predefined __clang__

2024-06-01 Thread Jonathan Wakely
On Fri, 31 May 2024 at 16:52, Alexandre Oliva wrote: > > On May 31, 2024, Jonathan Wakely wrote: > > > On 31/05/24 11:07 -0300, Alexandre Oliva wrote: > >> --- a/libstdc++-v3/include/pstl/pstl_config.h > [...] > >> -#if defined(__clang__) > >> +#if defined(__GLIBCXX__) ? defined(_GLIBCXX_CLANG) :

Re: [PATCH v2] [libstdc++] add _GLIBCXX_CLANG to workaround predefined __clang__

2024-06-01 Thread Jonathan Wakely
On Fri, 31 May 2024 at 18:43, Alexandre Oliva wrote: > > On May 31, 2024, Alexandre Oliva wrote: > > >> So either don't change this line at all, or just do a simple > >> s/__clang__/_GLIBCXX_CLANG/ > > > If c++config can be counted on, I'd be happy to do that, but I couldn't > > tell that it coul

[patch,avr,applied] Work around PR115307 early expanders generate bloat for isinf

2024-06-01 Thread Georg-Johann Lay
Applied this patch as proposed by Richard. Johann -- AVR: tree-optimization/115307 - Work around isinf bloat from early passes. PR tree-optimization/115307 gcc/ * config/avr/avr.md (SFDF): New mode iterator. (isinf2) [sf, df]: New expanders. gcc/testsuite/ * gc

[committed] libstdc++: Replace link to gcc-4.3.2 docs in manual [PR115269]

2024-06-01 Thread Jonathan Wakely
Pushed to trunk. I'll backport this, and link to the appropriate release branch docs instead of the trunk docs. -- >8 -- Link to the docs for GCC trunk instead. For the release branches, the link should be to the docs for appropriate release branch. Also replace the incomplete/outdated list of e

[pushed] wwwdocs: news: golang.org has become go.dev

2024-06-01 Thread Gerald Pfeifer
Pushed Gerald --- htdocs/news.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/news.html b/htdocs/news.html index b7a6f479..c319e250 100644 --- a/htdocs/news.html +++ b/htdocs/news.html @@ -582,7 +582,7 @@ We are currently accepting student applications. December

[PATCH] libstdc++: Implement C++26 features (P2546R5)

2024-06-01 Thread Jonathan Wakely
Here's an implementation of the C++26 header. We should really have some tests that invoke GDB and check that the breakpoint works when a debugger is attached. That seems tricky to do via the main conformance.exp testsuite. It could be done via the prettyprinters.exp testsuite, which already uses

[PATCH] libstdc++: Optimize std::basic_string_view::starts_with

2024-06-01 Thread Jonathan Wakely
We get smaller code at all optimization levels by not creating a temporary object, just comparing lengths first and then using traits_type::compare. This does less work than calling substr then operator==. libstdc++-v3/ChangeLog: * include/std/string_view (starts_with(basic_string_view)):

[PATCH 2/2] libstdc++: Reuse temporary buffer utils in

2024-06-01 Thread Jonathan Wakely
The non-throwing allocation logic in std::stacktrace duplicates the logic in , so we can just reuse those utilities. libstdc++-v3/ChangeLog: * include/std/stacktrace (basic_stacktrace::_Impl::_M_allocate): Use __detail::__get_temporary_buffer. (basic_stacktrace::_Impl::_M_

[PATCH 1/2] libstdc++: Handle extended alignment in std::get_temporary_buffer [PR105258]

2024-06-01 Thread Jonathan Wakely
I'v refactored the code a bit, adding a new __get_temporary_buffer helper, because I want to use that in in [PATCH 2/2]. I considered making __return_temporary_buffer also work for the non-sized case, using non-sized delete if __len == 0, and then making std::return_temporary_buffer call __return

[PATCH v2 1/2] libstdc++: Handle extended alignment in std::get_temporary_buffer [PR105258]

2024-06-01 Thread Jonathan Wakely
Although it's only used from places where we are allocating a sensible size, __detail::__get_temporary_buffer should really still check that len * sizeof(T) doesn't wrap around to zero and allocate a buffer that's smaller than expected. This v2 patch is the same as v1 except for adding this check:

[C PATCH, v3] Fix for redeclared enumerator initialized with different type [PR115109]

2024-06-01 Thread Martin Uecker
This is a new version of the patch. I changed the overflow warning to an error and added your other example to the test case. Bootstrapped and regression tested on x86_64. c23: Fix for redeclared enumerator initialized with different type [PR115109] c23 specifies that the type o

Re: [PATCH] c-family: Introduce the -Winvalid-noreturn flag from clang with extra tuneability

2024-06-01 Thread Julian Waters
Hi Jason, Thanks for the reply! I'll address your comments soon. I have a question, if there is an option defined in c.opt as an Enum, like fstrong-eval-order, and the -no variant of the option is passed, would the Var somehow reflect the negated option? Eg Winvalid-noreturn= C ObjC C++ ObjC++ Va

Re: [PATCH v2] [libstdc++] add _GLIBCXX_CLANG to workaround predefined __clang__

2024-06-01 Thread Jakub Jelinek
On Sat, Jun 01, 2024 at 09:21:53AM +0100, Jonathan Wakely wrote: > On Fri, 31 May 2024 at 18:43, Alexandre Oliva wrote: > > > > On May 31, 2024, Alexandre Oliva wrote: > > > > >> So either don't change this line at all, or just do a simple > > >> s/__clang__/_GLIBCXX_CLANG/ > > > > > If c++config

Re: [PATCH] jit: Ensure ssize_t is defined.

2024-06-01 Thread FX Coudert
ping**2 for this one-liner > Le 11 mai 2024 à 17:16, FX Coudert a écrit : > > Hi, > > On some targets it seems that ssize_t is not defined by any of the headers > transitively included by . This leads to a bootstrap fail when jit > is enabled. The attached patch fixes it by include . Other

Re: [PATCH] c-family: Introduce the -Winvalid-noreturn flag from clang with extra tuneability

2024-06-01 Thread Eric Gallager
On Sat, Jun 1, 2024 at 11:32 AM Julian Waters wrote: > > Hi Jason, > > Thanks for the reply! I'll address your comments soon. I have a > question, if there is an option defined in c.opt as an Enum, like > fstrong-eval-order, and the -no variant of the option is passed, would > the Var somehow refl

[pushed] analyzer: detect -Wanalyzer-allocation-size at call stmts [PR106203]

2024-06-01 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 r15-969-g2b0a7fe3abfbd4. gcc/analyzer/ChangeLog: PR analyzer/106203 * checker-event.h: Include "analyzer/event-loc-info.h".

Re: [PATCH] libstdc++: Implement C++26 features (P2546R5)

2024-06-01 Thread Ulrich Drepper
Hey Jon, I think we should give debuggers a chance to announce themselves by providing an entry point they can call (in the inferior) which sets a flag. A set flag plus a tracer PID would then be a sufficient indicator. The remaining code should also stay but some additional code can be added:

[pushed] wwwdocs: gcc-*/buildstat: Drop references to "Final Installation" docs

2024-06-01 Thread Gerald Pfeifer
Instructions for reporting a successful build are not actually part of the "Final Installation" docs (any more) and we have not been adding new build results for several years. --- htdocs/gcc-3.0/buildstat.html | 6 +- htdocs/gcc-3.1/buildstat.html | 6 +- htdocs/gcc-3.2/buildstat.html | 6

Re: [Patch, rs6000, aarch64, middle-end] Add implementation for different targets for pair mem fusion

2024-06-01 Thread Ajit Agarwal
Hello Richard: On 31/05/24 10:29 pm, Ajit Agarwal wrote: > Hello Richard: > > On 31/05/24 8:08 pm, Richard Sandiford wrote: >> Ajit Agarwal writes: >>> On 31/05/24 3:23 pm, Richard Sandiford wrote: Ajit Agarwal writes: > Hello All: > > Common infrastructure using generic code f

Re: [PATCH] ifcvt: Clarify if_info.original_cost.

2024-06-01 Thread Stefan Schulze Frielinghaus
On Fri, May 31, 2024 at 10:05:55PM -0600, Jeff Law wrote: > > > On 5/31/24 9:03 AM, Robin Dapp wrote: > > Hi, > > > > before noce_find_if_block processes a block it sets up an if_info > > structure that holds the original costs. At that point the costs of > > the then/else blocks have not been