Re: [PATCH] libgcobol, v2: Handle long double as an alternate IEEE754 128b

2025-04-11 Thread Rainer Orth
Hi Jakub, > On Wed, Apr 09, 2025 at 02:22:16PM +0200, Rainer Orth wrote: >> > Here is what I'm testing as an incremental fix, so far OK on x86_64-darwin >> > and powerpcle64 (GLIBC 2.34) .. others in progress. Does it help the >> > Solaris cases? >> >> I'll give it a try. Here's what I have (I

Re: [PATCH] libgcobol, v2: Handle long double as an alternate IEEE754 128b

2025-04-11 Thread Iain Sandoe
> On 11 Apr 2025, at 08:34, Rainer Orth wrote: > > Hi Jakub, > >> On Wed, Apr 09, 2025 at 02:22:16PM +0200, Rainer Orth wrote: Here is what I'm testing as an incremental fix, so far OK on x86_64-darwin and powerpcle64 (GLIBC 2.34) .. others in progress. Does it help the Solari

Re: [PATCH] libstdc++: Use constexpr-if for std::basic_string::_S_copy_chars

2025-04-11 Thread Tomasz Kaminski
On Thu, Apr 10, 2025 at 6:29 PM Jonathan Wakely wrote: > For C++11 and later we can remvoe four overloads of _S_copy_chars and > use constexpr-if in the generic _S_copy_chars. This simplifies overload > resolution for _S_copy_chars, and also means that we optimize for other > iterators such as st

Re: [PATCH] libgcobol, v2: Handle long double as an alternate IEEE754 128b

2025-04-11 Thread Jakub Jelinek
On Fri, Apr 11, 2025 at 09:34:32AM +0200, Rainer Orth wrote: > * amd64-pc-solaris2.11, which uses the libquadmath path: > > === cobol Summary for unix === > > # of expected passes 2925 > # of unexpected failures 108 > # of expected failures6 > # of unre

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

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 08:00, Tomasz Kaminski wrote: > > > > On Thu, Apr 10, 2025 at 6:53 PM Jonathan Wakely wrote: >> >> It would be good to provide a macOS definition of is_debugger_present as >> per https://developer.apple.com/library/archive/qa/qa1361/_index.html >> but that isn't included in

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

2025-04-11 Thread Jonathan Wakely
On Friday, 11 April 2025, Jonathan Wakely wrote: > On Fri, 11 Apr 2025 at 08:00, Tomasz Kaminski wrote: >> >> >> >> On Thu, Apr 10, 2025 at 6:53 PM Jonathan Wakely wrote: >>> >>> It would be good to provide a macOS definition of is_debugger_present as >>> per https://developer.apple.com/library/

RE: [EXTERNAL]Re: [PATCH] RISCV :Added MIPS P8700 Subtarget.

2025-04-11 Thread Umesh Kalappa
Thank you @Kito Cheng for early suggestions ,we will break down the patch like suggested and address the below comments . ~U -Original Message- From: Kito Cheng Sent: 11 April 2025 12:37 To: Umesh Kalappa Cc: gcc-patches@gcc.gnu.org; kito.ch...@sifive.com; Jesse Huang ; pal...@dabbel

[PATCH] cobol: Don't require GLOB_BRACE etc. [PR119217]

2025-04-11 Thread Rainer Orth
cdf-copy.cc doesn't compile on Solaris: /vol/gcc/src/hg/master/local/gcc/cobol/cdf-copy.cc: In member function ‘int copybook_elem_t::open_file(const char*, bool)’: /vol/gcc/src/hg/master/local/gcc/cobol/cdf-copy.cc:317:34: error: ‘GLOB_BRACE’ was not declared in this scope; did you mean ‘GLOB_ER

[PATCH] cobol: Initialize regmatch_t portably [PR119217]

2025-04-11 Thread Rainer Orth
The dts.h initialization of regmatch_t currently breaks Solaris compilation: In file included from /vol/gcc/src/hg/master/local/gcc/cobol/lexio.h:208, from /vol/gcc/src/hg/master/local/gcc/cobol/lexio.cc:36: /vol/gcc/src/hg/master/local/gcc/cobol/dts.h: In constructor ‘dts::csub_

[PATCH] cobol: Heed ASM_COMMENT_START

2025-04-11 Thread Rainer Orth
When building COBOL on Solaris/sparcv9 with the native assembler, many tests FAIL to assemble at -O0 like this: FAIL: cobol.dg/data1.cob -O0 (test for excess errors) Excess errors: /usr/ccs/bin/as: "/var/tmp//ccUduuqd.s", line 302: error: invalid character (0x50) /usr/ccs/bin/as: "/var/tmp//cc

[PATCH] cobol: Avoid conflict with OVERFLOW in system headers [PR119217]

2025-04-11 Thread Rainer Orth
parse.h causes the COBOL build to break on Solaris: cobol/parse.h:356:5: error: expected identifier before numeric constant 356 | OVERFLOW = 305,/* OVERFLOW */ | ^~~~ The problem is that has #define OVERFLOW3 To avoid the conflict, this patch renam

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

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 09:12, Jonathan Wakely wrote: > > On Fri, 11 Apr 2025 at 08:00, Tomasz Kaminski wrote: > > > > > > > > On Thu, Apr 10, 2025 at 6:53 PM Jonathan Wakely wrote: > >> > >> It would be good to provide a macOS definition of is_debugger_present as > >> per https://developer.apple

[PATCH] cobol: Avoid conflict with timespec_t in system headers [PR119217]

2025-04-11 Thread Rainer Orth
util.cc doesn't compile on Solaris: /vol/gcc/src/hg/master/local/gcc/cobol/util.cc:2135:7: error: using typedef-name ‘timespec_t’ after ‘class’ 2135 | class timespec_t { | ^~ This happens because declares timespec_t itself. In fact, POSIX.1 reserves every *_t identifier, s

[PATCH] libgcobol: Check for struct tm tm_zone

2025-04-11 Thread Rainer Orth
intrinsic.cc doesn't compile on Solaris: /vol/gcc/src/hg/master/cobol/libgcobol/intrinsic.cc: In function ‘void __gg__formatted_current_date(cblc_field_t*, cblc_field_t*, std::size_t, std::size_t)’: /vol/gcc/src/hg/master/cobol/libgcobol/intrinsic.cc:1480:6: error: ‘struct std::tm’ has no membe

[PATCH] libgcobol: Heed --enable-libgcobol

2025-04-11 Thread Rainer Orth
If some target isn't listed as supported in configure.tgt, --enable-libgcobol cannot override that. However, that's what should happen just like an explicit --enable-languages=cobol forces the frontend to be built. This patch, shamelessly adapted from libphobos, does just that. Tested on amd64-p

Re: [PATCH] aarch64: Fix CFA offsets in non-initial stack probes [PR119610]

2025-04-11 Thread Richard Sandiford
Richard Biener writes: > On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford > wrote: >> >> PR119610 is about incorrect CFI output for a stack probe when that >> probe is not the initial allocation. The main aarch64 stack probe >> function, aarch64_allocate_and_probe_stack_space, implicitly assum

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

2025-04-11 Thread Tomasz Kaminski
On Fri, Apr 11, 2025 at 10:13 AM Jonathan Wakely wrote: > On Fri, 11 Apr 2025 at 08:00, Tomasz Kaminski wrote: > > > > > > > > On Thu, Apr 10, 2025 at 6:53 PM Jonathan Wakely > wrote: > >> > >> It would be good to provide a macOS definition of is_debugger_present as > >> per https://developer.a

Re: [PATCH] libgcobol: Use strchr instead of index

2025-04-11 Thread Jakub Jelinek
On Fri, Apr 11, 2025 at 11:29:41AM +0200, Rainer Orth wrote: > valconf.cc doesn't compile on Solaris: > > cobol/valconv.cc: In function ‘bool __gg__string_to_numeric_edited(char*, > char*, int, int, const char*)’: > cobol/valconv.cc:856:40: error: ‘index’ was not declared in this scope; did > yo

[PATCH] libgcobol: Use strchr instead of index

2025-04-11 Thread Rainer Orth
valconf.cc doesn't compile on Solaris: cobol/valconv.cc: In function ‘bool __gg__string_to_numeric_edited(char*, char*, int, int, const char*)’: cobol/valconv.cc:856:40: error: ‘index’ was not declared in this scope; did you mean ‘Rindex’? 856 | const char *decimal_location = index(des

Re: [PATCH] cobol: Allow for undefined NAME_MAX [PR119217]

2025-04-11 Thread Andreas Schwab
On Apr 11 2025, Rainer Orth wrote: > All users of symbols.h fail to compile on Solaris: > > /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h: At global scope: > /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h:1365:13: error: ‘NAME_MAX’ > was not declared in this scope > 1365 | char name[NAME_

Re: [PATCH] libgcobol: Check for struct tm tm_zone

2025-04-11 Thread Andreas Schwab
On Apr 11 2025, Rainer Orth wrote: > This patch uses Autoconf's AC_STRUCT_TIMEZONE to determine its presence > and guard the use accordingly. You cannot use AC_STRUCT_TIMEZONE because it requires a link test (which is forbidden in a target module, see PR119550). -- Andreas Schwab, sch...@linux-

Re: [PATCH] cobol: Heed ASM_COMMENT_START

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 10:57 AM Rainer Orth wrote: > > When building COBOL on Solaris/sparcv9 with the native assembler, many > tests FAIL to assemble at -O0 like this: > > FAIL: cobol.dg/data1.cob -O0 (test for excess errors) > Excess errors: > /usr/ccs/bin/as: "/var/tmp//ccUduuqd.s", line 30

Re: [PATCH] cobol: Avoid conflict with OVERFLOW in system headers [PR119217]

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 11:03 AM Rainer Orth wrote: > > parse.h causes the COBOL build to break on Solaris: > > cobol/parse.h:356:5: error: expected identifier before numeric constant > 356 | OVERFLOW = 305,/* OVERFLOW */ > | ^~~~ > > The problem is that has >

Re: [PATCH] aarch64: Fix CFA offsets in non-initial stack probes [PR119610]

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 11:10 AM Richard Sandiford wrote: > > Richard Biener writes: > > On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford > > wrote: > >> > >> PR119610 is about incorrect CFI output for a stack probe when that > >> probe is not the initial allocation. The main aarch64 stack pr

Re: [PATCH] cobol: Initialize regmatch_t portably [PR119217]

2025-04-11 Thread Jakub Jelinek
On Fri, Apr 11, 2025 at 10:50:25AM +0200, Rainer Orth wrote: > 2025-04-08 Rainer Orth > > gcc/cobol: > PR cobol/119217 > * dts.h (csub_match): Initialize rm_so, rm_eo fields explicitly. > > # HG changeset patch > # Parent 6f227ddea0046a0164509bdb8069e96184304054 > cobol: In

Re: [PATCH] cobol: Avoid conflict with timespec_t in system headers [PR119217]

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 11:11 AM Rainer Orth wrote: > > util.cc doesn't compile on Solaris: > > /vol/gcc/src/hg/master/local/gcc/cobol/util.cc:2135:7: error: using > typedef-name ‘timespec_t’ after ‘class’ > 2135 | class timespec_t { > | ^~ > > This happens because declares

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

2025-04-11 Thread Maciej Cencora
Hi, unless I missed it, updates of std and std.compat modules are missing. Regards, Maciej

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

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 10:31, Tomasz Kaminski wrote: > > > > On Fri, Apr 11, 2025 at 10:13 AM Jonathan Wakely wrote: >> >> On Fri, 11 Apr 2025 at 08:00, Tomasz Kaminski wrote: >> > >> > >> > >> > On Thu, Apr 10, 2025 at 6:53 PM Jonathan Wakely wrote: >> >> >> >> It would be good to provide a ma

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

2025-04-11 Thread Jonathan Wakely
On Thu, 10 Apr 2025 at 17:52, Jonathan Wakely wrote: > > It would be good to provide a macOS definition of is_debugger_present as > per https://developer.apple.com/library/archive/qa/qa1361/_index.html > but that isn't included in this change. > > libstdc++-v3/ChangeLog: > > * config.h.in:

Re: [PATCH] aarch64: Fix CFA offsets in non-initial stack probes [PR119610]

2025-04-11 Thread Richard Sandiford
Richard Biener writes: > On Fri, Apr 11, 2025 at 11:10 AM Richard Sandiford > wrote: >> >> Richard Biener writes: >> > On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford >> > wrote: >> >> >> >> PR119610 is about incorrect CFI output for a stack probe when that >> >> probe is not the initial all

Re: [PATCH] aarch64: Fix CFA offsets in non-initial stack probes [PR119610]

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 12:18 PM Richard Sandiford wrote: > > Richard Biener writes: > > On Fri, Apr 11, 2025 at 11:10 AM Richard Sandiford > > wrote: > >> > >> Richard Biener writes: > >> > On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford > >> > wrote: > >> >> > >> >> PR119610 is about inco

Re: [PATCH] aarch64: Fix CFA offsets in non-initial stack probes [PR119610]

2025-04-11 Thread Richard Sandiford
Richard Sandiford writes: > Richard Biener writes: >> On Fri, Apr 11, 2025 at 11:10 AM Richard Sandiford >> wrote: >>> >>> Richard Biener writes: >>> > On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford >>> > wrote: >>> >> >>> >> PR119610 is about incorrect CFI output for a stack probe when th

[PATCH] libgomp: Update SVE test

2025-04-11 Thread Tejas Belagod
Fix udr-sve.c target test that to check for the correct results based on the OpenMP clauses used. The test was first written with a misunderstood functionality of the reduction clause. Tested with aarch64-linux-gnu. OK for trunk? libgomp/ChangeLog: * testsuite/libgomp.c-target/aarch64/u

Re: [PATCH v2] testcase: Add testcase for shrink wrapping of vector::push_back [PR118502]

2025-04-11 Thread Richard Sandiford
Andrew Pinski writes: > On Sun, Mar 9, 2025 at 1:35 PM Andrew Pinski wrote: >> >> LLVM folks noticed that GCC was shrink wrapping the call to >> vector::push_back. >> So I thought it was a good idea to commit a testcase to make sure GCC does >> not regress >> in this area unknowning. >> >> Note

Re: [PATCH] aarch64: Fix CFA offsets in non-initial stack probes [PR119610]

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 12:26 PM Richard Sandiford wrote: > > Richard Sandiford writes: > > Richard Biener writes: > >> On Fri, Apr 11, 2025 at 11:10 AM Richard Sandiford > >> wrote: > >>> > >>> Richard Biener writes: > >>> > On Thu, Apr 10, 2025 at 10:10 PM Richard Sandiford > >>> > wrote: >

Re: [PATCH] libstdc++: Use constexpr-if for std::basic_string::_S_copy_chars

2025-04-11 Thread Jonathan Wakely
On 11/04/25 09:49 +0200, Tomasz Kaminski wrote: On Thu, Apr 10, 2025 at 6:29 PM Jonathan Wakely wrote: For C++11 and later we can remvoe four overloads of _S_copy_chars and use constexpr-if in the generic _S_copy_chars. This simplifies overload resolution for _S_copy_chars, and also means that

PowerPC patch ping^2

2025-04-11 Thread Jakub Jelinek
On Wed, Apr 02, 2025 at 03:32:31PM +0200, Jakub Jelinek wrote: > I'd like to ping the following PowerPC patches: > > https://gcc.gnu.org/pipermail/gcc-patches/2025-March/679312.html > rs6000: Ignore OPTION_MASK_SAVE_TOC_INDIRECT differences in inlining > decisions [PR119327] > > https://gcc.gnu.

[committed] d: Merge upstream dmd 1b34fea478, phobos 40ffbb364

2025-04-11 Thread Iain Buclaw
Hi, This patch merges the D front-end compiler with upstream dmd 1b34fea478, and the standard runtime library with upstream phobos 40ffbb364. Synchronizing the recent bug fixes targeted for v2.111.1. D front-end changes: - Import latest fixes from dmd v2.111.1-rc.1. Phobos changes:

[PATCH] libstdc++: Define __cpp_lib_containers_ranges in appropariate headers [PR111055]

2025-04-11 Thread Tomasz Kamiński
This is final piece of P1206R7, adding a feature test macros, as range constructors and member operations are now implemented for all containers and adaptors. For consistency with the proposal, all new container operations and helpers are now defined if __glibcxx_containers_ranges, instead of __gl

Re: [PATCH] libstdc++: Use constexpr-if for std::basic_string::_S_copy_chars

2025-04-11 Thread Tomasz Kaminski
On Fri, Apr 11, 2025 at 12:52 PM Jonathan Wakely wrote: > On 11/04/25 09:49 +0200, Tomasz Kaminski wrote: > >On Thu, Apr 10, 2025 at 6:29 PM Jonathan Wakely > wrote: > > > >> For C++11 and later we can remvoe four overloads of _S_copy_chars and > >> use constexpr-if in the generic _S_copy_chars.

[PATCH] libstdc++: Implement formatter for ranges and range_formatter [PR109162]

2025-04-11 Thread Tomasz Kamiński
This patch implements formatter specialization for input_ranges and range_formatter class form P2286R8, as adjusted by P2585R1. The formatter for pair/tuple is not yet provided (making map unusable). To indicate partial support we define __glibcxx_format_ranges macro value 1, without defining __cp

Re: [PATCH] libgomp: Update SVE tests

2025-04-11 Thread Tejas Belagod
On 4/10/25 5:29 PM, Jakub Jelinek wrote: On Thu, Apr 10, 2025 at 05:13:12PM +0530, Tejas Belagod wrote: Thanks for the explanation. I looked into why some of the tests may have failed - my flawed understanding of the reduction clause was why I didn't have the += in the loops - it might have pas

Re: [PATCH] libstdc++: Define __cpp_lib_containers_ranges in appropariate headers [PR111055]

2025-04-11 Thread Jonathan Wakely
Spelling of "appropriate" in the summary line. On 11/04/25 13:18 +0200, Tomasz Kamiński wrote: This is final piece of P1206R7, adding a feature test macros, as range constructors and member operations are now implemented for all containers and adaptors. For consistency with the proposal, all

[PATCH] cobol: Allow for undefined NAME_MAX [PR119217]

2025-04-11 Thread Rainer Orth
All users of symbols.h fail to compile on Solaris: /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h: At global scope: /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h:1365:13: error: ‘NAME_MAX’ was not declared in this scope 1365 | char name[NAME_MAX]; | ^~~~ NAME_MAX be

Re: [PATCH] libstdc++: Define __cpp_lib_containers_ranges in appropariate headers [PR111055]

2025-04-11 Thread Tomasz Kaminski
On Fri, Apr 11, 2025 at 1:38 PM Jonathan Wakely wrote: > > Spelling of "appropriate" in the summary line. > > On 11/04/25 13:18 +0200, Tomasz Kamiński wrote: > >This is final piece of P1206R7, adding a feature test macros, > >as range constructors and member operations are now implemented for > >

[PATCH]RISCV :Added MIPS P8700 Subtarget

2025-04-11 Thread Umesh Kalappa
This is the first patch from the two-patch series, where configured gcc for P8700 micro architecture in the first patch and Tested with dejagnu riscv.exp tests for --mtune=mips-p8700. P8700 is a high-performance processor from MIPS by extending RISCV. The following changes enable P8700 proces

Re: [PATCH] libstdc++: Use constexpr-if for std::basic_string::_S_copy_chars

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 12:21, Tomasz Kaminski wrote: > > > > On Fri, Apr 11, 2025 at 12:52 PM Jonathan Wakely wrote: >> >> On 11/04/25 09:49 +0200, Tomasz Kaminski wrote: >> >On Thu, Apr 10, 2025 at 6:29 PM Jonathan Wakely wrote: >> > >> >> For C++11 and later we can remvoe four overloads of _S_

Re: [PATCH] libgcobol: Check for struct tm tm_zone

2025-04-11 Thread Rainer Orth
Hi Andreas, > On Apr 11 2025, Rainer Orth wrote: > >> This patch uses Autoconf's AC_STRUCT_TIMEZONE to determine its presence >> and guard the use accordingly. > > You cannot use AC_STRUCT_TIMEZONE because it requires a link test (which > is forbidden in a target module, see PR119550). drats. Mu

Re: [PATCH] cobol: Avoid conflict with OVERFLOW in system headers [PR119217]

2025-04-11 Thread Simon Sobisch
Shouldn't that be --- a/gcc/cobol/parse.y +++ b/gcc/cobol/parse.y @@ -337,7 +337,7 @@ %token INVALID %token NUMBER NEGATIVE %token NUMSTR"numeric literal" -%token OVERFLOW +%token OVERFLOW_kw "OVERFLOW" %token COMPUTATIONAL ? Otherwise biso

Re: [PATCH] libstdc++: Fix atomic CAS hang with C++11 [PR114865]

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 08:23, Tomasz Kaminski wrote: > > > > On Thu, Apr 10, 2025 at 6:27 PM Jonathan Wakely wrote: >> >> The std::atomic constructor clears padding bits so that compare_exchange >> will not fail due to differences in padding bits. But we can only do >> that for C++14 and later, b

Re: [PATCH] cobol: Allow for undefined NAME_MAX [PR119217]

2025-04-11 Thread Simon Sobisch
> You're right: seems to be all about COBOL function names. No idea what value is appropriate/required here, though. if this is about COBOL internal function names: ISO says and GnuCOBOL therefore defines /* Maximum length of COBOL words */ #define COB_MAX_WORDLEN 63 Note that _extern

Re: [PATCH] cobol: Avoid conflict with OVERFLOW in system headers [PR119217]

2025-04-11 Thread Rainer Orth
Hi Simon, > Shouldn't that be > > --- a/gcc/cobol/parse.y > +++ b/gcc/cobol/parse.y > @@ -337,7 +337,7 @@ > %token INVALID > %token NUMBER NEGATIVE > %token NUMSTR"numeric literal" > -%token OVERFLOW > +%token OVERFLOW_kw "OVERFLOW" > %token C

Re: [PATCH] cobol: Allow for undefined NAME_MAX [PR119217]

2025-04-11 Thread Richard Biener
On Fri, Apr 11, 2025 at 2:14 PM Rainer Orth wrote: > > Andreas Schwab writes: > > > On Apr 11 2025, Rainer Orth wrote: > > > >> All users of symbols.h fail to compile on Solaris: > >> > >> /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h: At global scope: > >> /vol/gcc/src/hg/master/local/gcc/co

ping on fixes for cobol.1 + gcobc

2025-04-11 Thread Simon Sobisch
with GCC 15.1 in sight... ping on gcobc wrapper fixes and additions: https://gcc.gnu.org/pipermail/gcc-patches/2025-April/680218.html (note: obviously it would be good if -Wall [1] would work (the "global" PR for -Wall was postponed to GCC16, so possibly add to gcobol as intermediate?), then

Re: [PATCH] dwarf2out: Decrease dw_loc_descr_node and dw_attr_struct struct sizes [PR119711]

2025-04-11 Thread Richard Biener
On Thu, 10 Apr 2025, Jakub Jelinek wrote: > Hi! > > As noted by Richi on a large testcase, there are unnecessary paddings > in some heavily used dwarf2out.{h,cc} structures on 64-bit hosts. > > struct dw_val_node { > enum dw_val_class val_class;/* 0 4 */ > >

[committed] libstdc++: Add fast_float patch to LOCAL_PATCHES

2025-04-11 Thread Jonathan Wakely
libstdc++-v3/ChangeLog: * src/c++17/fast_float/LOCAL_PATCHES: Update. --- Pushed to trunk. libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES | 1 + 1 file changed, 1 insertion(+) diff --git a/libstdc++-v3/src/c++17/fast_float/LOCAL_PATCHES b/libstdc++-v3/src/c++17/fast_float/LOCAL_PATCH

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

2025-04-11 Thread Jonathan Wakely
This includes the P2810R4 (is_debugger_present is_replaceable) changes, allowing std::is_debugger_present to be replaced by the program. It would be good to provide a macOS definition of is_debugger_present as per https://developer.apple.com/library/archive/qa/qa1361/_index.html but that isn't inc

[PATCH] libstdc++: Document thread-safety for COW std::string [PR21334]

2025-04-11 Thread Jonathan Wakely
The gcc4-compatible copy-on-write std::string does not conform to the C++11 requirements on data race avoidance in standard containers. Specifically, calling non-const member functions such as begin() and data() needs to do the "copy on write" operation and so is most definitely a modification of t

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Qing Zhao
> On Apr 10, 2025, at 11:12, Martin Uecker wrote: > > Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyarekar: >> On 2025-04-10 10:50, Andrew MacLeod wrote: >>> Its not clear to me exactly what is being asked, but I think the >>> suggestion is that pointer references are being

[committed] [RISC-V] Fix testsuite fallout from recent changes

2025-04-11 Thread Jeff Law
Recent changes have started triggering: Tests that now fail, but worked before (3 tests): unix/-march=rv64gc_zba_zbb_zbs_zicond: gcc: gcc.target/riscv/rvv/base/pr115068-run.c (test for excess errors) unix/-march=rv64gc_zba_zbb_zbs_zicond: gcc: gcc.target/riscv/rvv/base/pr115068.c (test for ex

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Qing Zhao
> On Apr 10, 2025, at 10:55, Siddhesh Poyarekar wrote: > > On 2025-04-10 10:50, Andrew MacLeod wrote: >> Its not clear to me exactly what is being asked, but I think the suggestion >> is that pointer references are being replaced with a builtin function called >> .ACCESS_WITH_SIZE ?and I

[pushed] c++: avoid ARM -Wunused-value [PR114970]

2025-04-11 Thread Jason Merrill
Tested by me on x86_64-pc-linux-gnu and Sam James on armv7a-unknown-linux-gnueabihf, applying to trunk. -- 8< -- Because of the __builtin_is_constant_evaluated, maybe_constant_init in expand_default_init fails, so the constexpr constructor isn't folded until cp_fold, which then calls cp_build_ini

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Andrew MacLeod
On 4/11/25 10:05, Qing Zhao wrote: On Apr 10, 2025, at 10:55, Siddhesh Poyarekar wrote: On 2025-04-10 10:50, Andrew MacLeod wrote: Its not clear to me exactly what is being asked, but I think the suggestion is that pointer references are being replaced with a builtin function called .ACC

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Martin Uecker
Am Freitag, dem 11.04.2025 um 10:42 -0400 schrieb Andrew MacLeod: > On 4/11/25 10:27, Qing Zhao wrote: > > > > > On Apr 10, 2025, at 11:12, Martin Uecker wrote: > > > > > > Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyarekar: > > > > On 2025-04-10 10:50, Andrew MacLeod wrote:

Re: [PATCH] libstdc++: Fix atomic CAS hang with C++11 [PR114865]

2025-04-11 Thread Tomasz Kaminski
On Fri, Apr 11, 2025 at 2:25 PM Jonathan Wakely wrote: > On Fri, 11 Apr 2025 at 08:23, Tomasz Kaminski wrote: > > > > > > > > On Thu, Apr 10, 2025 at 6:27 PM Jonathan Wakely > wrote: > >> > >> The std::atomic constructor clears padding bits so that compare_exchange > >> will not fail due to dif

Re: [committed] modula2: Fix a comment typo

2025-04-11 Thread Gaius Mulley
Jakub Jelinek writes: > Hi! > > During make gcc.pot I've noticed among tons of other warnings (e.g. because > can't appears in non-C/C++ style comment and so gettext considers it > unterminated) a warning where the lack of " looked unintentional. > > Committed to trunk as obvious. > > 2025-04-09

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Qing Zhao
> On Apr 11, 2025, at 10:42, Andrew MacLeod wrote: > > > On 4/11/25 10:27, Qing Zhao wrote: >> >>> On Apr 10, 2025, at 11:12, Martin Uecker wrote: >>> >>> Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyarekar: On 2025-04-10 10:50, Andrew MacLeod wrote: > Its not c

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

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 14:47, Jonathan Wakely wrote: > > This includes the P2810R4 (is_debugger_present is_replaceable) changes, > allowing std::is_debugger_present to be replaced by the program. > > It would be good to provide a macOS definition of is_debugger_present as > per https://developer.a

[PATCH] Fix PR target/119673

2025-04-11 Thread Eric Botcazou
Hi, this applies the same magic to config/i386/gthr-win32.h that was applied to gthr-posix.h (https://gcc.gnu.org/cgit/gcc/commit/?id=6a4d1c374eed17) for the sake of C++ modules (thanks to Andrew for the pointer!). Built for {i686,x86_64}-w64-mingw32, OK for the mainline? 2025-04-11 Eric Botc

[PHASE1 PATCH] Use optimize free lists for alloc_pages

2025-04-11 Thread Andi Kleen
Right now ggc has a single free list for multiple sizes. In some cases the list can get mixed by orders and then the allocator may spend a lot of time walking the free list to find the right sizes. This patch splits the free list into multiple free lists by order which allows O(1) access in most c

[PATCH] Add diffsummary.py to contrib

2025-04-11 Thread Andi Kleen
This adds an automatic downloader for the latest test results from the mailing list archive and supports diffing test_summary to it. Useful if you don't want to run your own baseline. contrib/ChangeLog: * diffsummary.py: New file. --- contrib/diffsummary.py | 104

Re: [PATCH V2] RISC-V: Add support for Zalasr extension

2025-04-11 Thread Andrea Parri
On Thu, Apr 10, 2025 at 02:48:36PM -0700, Edwin Lu wrote: > [1] https://github.com/riscv/riscv-zalasr > > Add minimal support for the zalasr (load-acquire/store-release) > extension > > Currently there is no toggle to opt into the abi-breaking note 3 > mappings in the PSABI doc so support for tha

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Andrew MacLeod
On 4/11/25 11:36, Qing Zhao wrote: On Apr 11, 2025, at 10:42, Andrew MacLeod wrote: On 4/11/25 10:27, Qing Zhao wrote: On Apr 10, 2025, at 11:12, Martin Uecker wrote: Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyarekar: On 2025-04-10 10:50, Andrew MacLeod wrote: It

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Qing Zhao
> On Apr 11, 2025, at 10:53, Martin Uecker wrote: > > Am Freitag, dem 11.04.2025 um 10:42 -0400 schrieb Andrew MacLeod: >> On 4/11/25 10:27, Qing Zhao wrote: >>> On Apr 10, 2025, at 11:12, Martin Uecker wrote: Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyar

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Martin Uecker
Am Freitag, dem 11.04.2025 um 16:01 + schrieb Qing Zhao: > > > On Apr 11, 2025, at 10:53, Martin Uecker wrote: > > > > Am Freitag, dem 11.04.2025 um 10:42 -0400 schrieb Andrew MacLeod: > > > On 4/11/25 10:27, Qing Zhao wrote: > > > > > > > > > On Apr 10, 2025, at 11:12, Martin Uecker wrote

[patch, Fortran] Fix PR 119669

2025-04-11 Thread Thomas Koenig
Hello world, the attached patch fixes an ICE by setting the typespec of a dummy argument from a global function if known. plus setting the correct flag. This also removes the corresponding assert. I'm not quite sure that the code with the subroutine attribute can be reached, but I thought better

Re: [PATCH] cobol: Allow for undefined NAME_MAX [PR119217]

2025-04-11 Thread Rainer Orth
Andreas Schwab writes: > On Apr 11 2025, Rainer Orth wrote: > >> All users of symbols.h fail to compile on Solaris: >> >> /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h: At global scope: >> /vol/gcc/src/hg/master/local/gcc/cobol/symbols.h:1365:13: error: ‘NAME_MAX’ >> was not declared in this

Re: [PATCH] testsuite: arm: rename arm_v8_1_lob_ok into arm_v8_1_lob_hw

2025-04-11 Thread Christophe Lyon
Hi! On Thu, 10 Apr 2025 at 19:13, Richard Earnshaw (lists) wrote: > > On 10/04/2025 14:55, Christophe Lyon wrote: > > All arm effective-targets using check_runtime use the "_hw" or > > "_multilib" suffix, so rename arm_v8_1_lob_ok into arm_v8_1_lob_hw for > > consistency. > > > > gcc/testsuite/Ch

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Andrew MacLeod
On 4/11/25 10:27, Qing Zhao wrote: On Apr 10, 2025, at 11:12, Martin Uecker wrote: Am Donnerstag, dem 10.04.2025 um 10:55 -0400 schrieb Siddhesh Poyarekar: On 2025-04-10 10:50, Andrew MacLeod wrote: Its not clear to me exactly what is being asked, but I think the suggestion is that pointe

[PATCH] testsuite: arm: Fix unsigned-extend-2.c [PR116445]

2025-04-11 Thread Christophe Lyon
The test was designed to pass with thumb2, but code generation changed with the introduction of Low Overhead Loops, so the test can fail if one overrides the flags when running the testsuite. In addition, useless subtract / extension instructions require -O2 to remove them (-O is not sufficient),

Re: [PATCH] LRA: Backport PR115568 and PR119689 to release branches

2025-04-11 Thread Vladimir Makarov
On 4/11/25 2:29 AM, Uros Bizjak wrote: Hello! I would like to backport PR115568 and PR119689 to release branches. Author: Richard Biener Date: Wed Apr 9 14:36:19 2025 +0200 rtl-optimization/119689 - compare-debug failure with LRA The previous change to fix LRA rematerialization b

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Qing Zhao
> On Apr 11, 2025, at 12:20, Martin Uecker wrote: > > Am Freitag, dem 11.04.2025 um 16:01 + schrieb Qing Zhao: >> >>> On Apr 11, 2025, at 10:53, Martin Uecker wrote: >>> >>> Am Freitag, dem 11.04.2025 um 10:42 -0400 schrieb Andrew MacLeod: On 4/11/25 10:27, Qing Zhao wrote: > >

Re: [patch, Fortran] Fix PR 119669

2025-04-11 Thread Harald Anlauf
Hi Thomas! Am 11.04.25 um 17:50 schrieb Thomas Koenig: Hello world, the attached patch fixes an ICE by setting the typespec of a dummy argument from a global function if known. plus setting the correct flag. This also removes the corresponding assert.  I'm not quite sure that the code with the

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Martin Uecker
Am Freitag, dem 11.04.2025 um 17:08 + schrieb Qing Zhao: > > > On Apr 11, 2025, at 12:20, Martin Uecker wrote: > > > > Am Freitag, dem 11.04.2025 um 16:01 + schrieb Qing Zhao: > > > > > > > On Apr 11, 2025, at 10:53, Martin Uecker wrote: > > > > > > > > Am Freitag, dem 11.04.2025 um 1

Re: [PATCH] libstdc++: Fix atomic CAS hang with C++11 [PR114865]

2025-04-11 Thread Jonathan Wakely
On Fri, 11 Apr 2025 at 15:14, Tomasz Kaminski wrote: > > > > On Fri, Apr 11, 2025 at 2:25 PM Jonathan Wakely wrote: >> >> On Fri, 11 Apr 2025 at 08:23, Tomasz Kaminski wrote: >> > >> > >> > >> > On Thu, Apr 10, 2025 at 6:27 PM Jonathan Wakely wrote: >> >> >> >> The std::atomic constructor clear

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Siddhesh Poyarekar
On 2025-04-11 13:37, Martin Uecker wrote: My understanding is that such issue with the implicit data flow dependency information missing is only for the counted_by attribute, not for the other TYPE which already have the bound information there. The dependency issue is only for the size, but

[PATCH] [testsuite] [ppc] compile [PR112822] with -mvsx

2025-04-11 Thread Alexandre Oliva
g++.dg/pr112822.C uses altivec vectors explicitly, but it expects this feature to be enabled by default on targets that recognize the attribute, which is not a given on older ppc cpus, where the compiler recommends recompiling with -mvsx. Since it's just a compilation test, we don't seem to need t

[PATCH] [testsuite] [ppc] require float128 available for copysign

2025-04-11 Thread Alexandre Oliva
The rs6000.md copysign3 expander requires the mode to satisfy FLOAT128_IEEE_P, so requiring float128 on ppc for ifn_copysign effective target is hopefully a close-enough approximation. gcc.dg/fold-copysign-1.c and gcc.dg/pr55152-2.c fail on ppc-elf without this. Regstrapped on powerpc64le-linux

[PATCH] [testsuite] [ppc] ipa-sra-19.c: pass -Wno-psabi on powerpc-*-elf as well

2025-04-11 Thread Alexandre Oliva
Like other ppc targets, powerpc-*-elf needs -Wno-psabi to compile gcc.dg/ipa/ipa-sra-19.c without an undesired warning about vector argument passing. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install? for gcc/testsuite/ChangeLog

[PATCH] [testsuite] [ppc] add -mfloat128 to __ieee128-using bfp tests

2025-04-11 Thread Alexandre Oliva
Some ppc bfp tests use __ieee128 without ensuring it's available. Require ppc_ieee128_ok, add -mfloat128 to get the type defined, and tolerate the warning that this option may trigger. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install?

[PATCH] [testsuite] [ppc] xfail pr52451.c on ppc [PR58684]

2025-04-11 Thread Alexandre Oliva
Like pr91323.c, pr52451.c fails on all powerpc variants (except where already skipped), because it uses fcmpu even when qNaNs should flag FP exceptions. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install? for gcc/testsuite/ChangeLog

[PATCH] [testsuite] [ppc] newlib sets FE_VXSOFT on raise FE_INVALID

2025-04-11 Thread Alexandre Oliva
The implementation of the fe*except primitives in newlib sets the FE_VXSOFT bit when raising FE_INVALID, and the test doesn't expect that. Skip it: the tested builtin expansions are for glibc only anyway. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-e

[PATCH] [testsuite] [ppc] disable -mpowerpc64 for various ilp32 asm-out checks

2025-04-11 Thread Alexandre Oliva
Multiple tests on ilp32 get TARGET_POWERPC64 enabled by -mdejagnu-cpu options, but the results they expect are only attained without enabling it, so disable it explicitly. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install? for gcc/tes

[PATCH] [testsuite] [ppc] block-cmp-8 should require powerpc64

2025-04-11 Thread Alexandre Oliva
gcc.target/powerpc/block-cmp-8.c is an execution test on ilp32. It tests for support for the 64-bit ISA in the compiler, but not for the ability to execute powerpc64 instructions, so the test fails on 32-bit hardware. Require powerpc64 instead. Regstrapped on powerpc64le-linux-gnu. Also teste

Re: .ACCESS_WITH_SIZE and pointer ranges

2025-04-11 Thread Martin Uecker
Am Freitag, dem 11.04.2025 um 13:55 -0400 schrieb Siddhesh Poyarekar: > On 2025-04-11 13:37, Martin Uecker wrote: > > > My understanding is that such issue with the implicit data flow > > > dependency information missing is only for the > > > counted_by attribute, not for the other TYPE which alre

[PATCH] [testsuite] [ppc] add -mfloat128 to pr67808.c

2025-04-11 Thread Alexandre Oliva
gcc.target/powerpc/pr67808.c in some cases expects both 128-bit long double types to be defined, but -mlong-double-128 doesn't guarantee that without -mfloat128 on targets that would get the IEEE128 type as long double. Add -mfloat128 to ensure the desired IBM 128-bit floating-point type is avai

[PATCH] [testsuite] [ppc] add -mdejagnu-cpu=power7 to pr17381.c

2025-04-11 Thread Alexandre Oliva
Below power7, it seems to be more profitable to compress the floating-point constants and use an additional fp register move to "extend" it. Only at power7 and above do we keep the constants separate and load them, getting to the expected 'fmr' count. Regstrapped on powerpc64le-linux-gnu. Also

[PATCH] [testsuite] [ppc] add -maltivec to pr111380-2.c

2025-04-11 Thread Alexandre Oliva
gcc.target/powerpc/pr111380-2.c requires altivec to be enabled to hit the expected option mismatch and inline error, so enable it after checking for compiler support. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install? for gcc/testsuit

[PATCH] [testsuite] [ppc] require ifunc for target_clones test

2025-04-11 Thread Alexandre Oliva
gcc.target/powerpc/power11-3.c uses target_clones, that depends on ifunc. Require ifunc support. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install? for gcc/testsuite/ChangeLog * gcc.target/powerpc/power11-3.c: Require ifunc

[PATCH] [testsuite] [ppc] add -mno-strict-align to pr111449-1.c

2025-04-11 Thread Alexandre Oliva
gcc.target/powerpc/pr111449-1.c's expected results only come about without strict alignment, so disable it explicitly. Regstrapped on powerpc64le-linux-gnu. Also tested with gcc-14 on x86_64-linux-x-powerpc-elf. Ok to install? for gcc/testsuite/ChangeLog * gcc.target/powerpc/pr1114

  1   2   >