Re: [PATCH] COBOL 3/15 92K bld: config and build machinery

"James K. Lowden" writes: > On Sat, 15 Feb 2025 21:18:50 +0000 > Sam James wrote: > >> Please generate these files with vanilla autoconf-2.69, not >> distro-patched autoconf. > > Sure thing, Sam. I meant to do that; I thought I did. It might be that the

Re: [PATCH] COBOL 12/15 24K pos: Posix adapter framework

"James K. Lowden" writes: > On Sat, 15 Feb 2025 21:24:52 +0000 > Sam James wrote: > >> > +prototypes.cpp: posix.txt >> > + awk -F'[/.]' '{ print $$6 }' $^ | \ >> > + while read F; do echo "/* $$F */" && man 2

Re: [PATCH] COBOL 5/15 380K hdr: header files

"James K. Lowden" writes: > On Sat, 15 Feb 2025 21:30:16 +0000 > Sam James wrote: > >> > + * This stand-in for std::regex was written because the >> > implementation provided >> > + * by the GCC libstdc++ in GCC 11 proved too slow, where "

Re: [PATCH] COBOL 6/15 156K lex: lexer

"James K. Lowden" writes: > On Sat, 15 Feb 2025 23:32:37 -0500 > David Malcolm wrote: > > In defense of lack of free(3) ... > >> > +const char * >> > +esc( size_t len, const char input[] ) { >> > +  static char spaces[] = "([,;]?[[:space:]])+"; >> > +  static char spaceD[] = "(\n {6}D" "|" "[,;]

Re: [PATCH] builtins: Ensure sin and cos properly set errno when INFINITY is passed [PR80042]

Peter Damianov writes: > POSIX says that sin and cos should set errno to EDOM when infinity is passed > to > them. Make sure this is accounted for in builtins.def, and add tests. > > gcc/ > PR middle-end/80042 > * builtins.def: (sin|cos)(f|l) can set errno. > gcc/testsuite/ > *

Re: [PATCH] i386: Implement Thread Local Storage on Windows

Julian Waters writes: > Apologies, here is the implementation with regenerated configure this time. > Do excuse me sending an entirely new mail instead of replying to the previous > one, I have to do it this way due to a quirk in my email client. > > best regards, > Julian > > gcc/ChangeLog: >

Re: [PATCH htdocs] bugs: Link to all 'Porting to' docs in 'Common problems when upgrading ...'

Sam James writes: > Suggested by Andrew Pinski. I think it makes sense to have it in here even > if perhaps a bit verbose, because we really try to tell bug reporters to > read the page properly. > > This could also be a table. Ping on this if I may.

Re: [PATCH htdocs 1/2] bugs: improve "ABI changes" subsection

nd myself citing this section a few times recently and don't want people to get the wrong idea). > > > > On Wed, 12 Feb 2025 at 09:30, Sam James wrote: >> >> C++ ABI for C++ standards with full support by GCC (rather than those >> marked as experimental per https

Re: [RFC] PR81358: Enable automatic linking of libatomic

Sam James writes: > Prathamesh Kulkarni writes: > >>> -Original Message- >>> From: Prathamesh Kulkarni >>> Sent: 10 January 2025 09:48 >>> To: Thomas Schwinge >>> Cc: Tobias Burnus ; Joseph Myers >>> ; Xi Ruoyao ; Matth

Re: [PATCH] i386: Verify that argument registers are spilled properly

Uros Bizjak writes: > On Sun, Mar 9, 2025 at 3:05 PM H.J. Lu wrote: >> >> RDI, RSI, RDX and RCX registers are used to pass arguments in 64-bit >> mode. EAX, EDX and ECX registers are used to pass arguments in 32-bit >> mode. Add tests to verify that argument registers are spilled properly. >>

Re: [PATCH htdocs] bugs: Link to all 'Porting to' docs in 'Common problems when upgrading ...'

Gerald Pfeifer writes: > On Wed, 12 Feb 2025, Sam James wrote: >> Suggested by Andrew Pinski. I think it makes sense to have it in here >> even if perhaps a bit verbose, because we really try to tell bug >> reporters to read the page properly. > > Makes sense. >

[PATCH htdocs] bugs: Link to all 'Porting to' docs in 'Common problems when upgrading ...'

Suggested by Andrew Pinski. I think it makes sense to have it in here even if perhaps a bit verbose, because we really try to tell bug reporters to read the page properly. --- This takes into account Gerald's comments, hopefully faithfully. Gerald, let me know if I misinterpreted anything or need

[PATCH htdocs 1/2] gcc-4.8/porting_to: update link to archive of Fedora rebuild

--- Pushed. htdocs/gcc-4.8/porting_to.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/htdocs/gcc-4.8/porting_to.html b/htdocs/gcc-4.8/porting_to.html index 9ed0d06b..c7e188ef 100644 --- a/htdocs/gcc-4.8/porting_to.html +++ b/htdocs/gcc-4.8/porting_to.html @@ -231,7 +231,7

[PATCH htdocs 2/2] gcc-8/porting_to: link to Fedora mass rebuild post

As is done for other releases. --- Pushed. htdocs/gcc-8/porting_to.html | 6 -- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/htdocs/gcc-8/porting_to.html b/htdocs/gcc-8/porting_to.html index d24ea347..1d16a29e 100644 --- a/htdocs/gcc-8/porting_to.html +++ b/htdocs/gcc-8/porti

Re: The COBOL front end -- The Initial Onslaught

Robert Dubner writes: > > I need to be able to change, at the very least, the Assignment field. I > don't seem to have any way of doing that. Make sure your email address on Bugzilla is x...@gcc.gnu.org. Using that address grants the account editbugs privileges. sam

Re: [PATCH] Add Robert Dubner to Maintainers

Robert Dubner writes: >> -Original Message- >> From: Jakub Jelinek >> Sent: Tuesday, March 11, 2025 17:40 >> To: Robert Dubner >> Cc: gcc-patches@gcc.gnu.org >> Subject: Re: [PATCH] Add Robert Dubner to Maintainers >> >> On Tue, Mar 11, 2025 at 02:24:26PM -0500, Robert Dubner wrote: >>

Re: [PATCH][v3] Simple cobol.dg testsuite

Simon Sobisch writes: > Thanks for your work on adding a testsuite. Can you please explain why > you do this when a complete testsuite exists in autoconf (autotest) > format (which roots back to decade of work in GnuCOBOL, with all > copyrights for that already with the FSF)? > I don't think any

Re: [r15-7532 Regression] FAIL: g++.dg/asan/pr118763.C -Os execution test on Linux/x86_64

"haochen.jiang" writes: > On Linux/x86_64, > > e96e1bb69c7b46db18e747ee379a62681bc8c82d is the first bad commit > commit e96e1bb69c7b46db18e747ee379a62681bc8c82d > Author: Jason Merrill > Date: Fri Feb 14 10:53:01 2025 +0100 > > c++: extended temp cleanups [PR118856] > > caused > > FAIL: g

Re: [PATCH] libstdc++: Allow 'configure.host' to modify 'EXTRA_CFLAGS', 'EXTRA_CXX_FLAGS'

Thomas Schwinge writes: > In particular, 'GLIBCXX_ENABLE_CXX_FLAGS' shouldn't overwrite > 'EXTRA_CXX_FLAGS' > (and prepend any additional '--enable-cxx-flags=[...]'). Why 'CXX_FLAGS' spelling (which is unusual) rather than 'CXXFLAG-- ah, I see we have a load of EXTRA_CXXFLAGS, and then a lot of

Re: [PATCH] doc: document incremental LTO flags

Michal Jires writes: > On Thu, 2025-03-27 at 15:33:44 +0000, Sam James wrote: >> >> One thing I wasn't quite sure on yet: is -flto-partition=cache automatic >> with -flto-incremental? Or is it just an optional flag I can pass for >> more effective incrementa

Re: [PATCH] testsuite: arm: Fix dg-final in short-vfp-1.c [PR119556]

Christophe Lyon writes: > Recent syntactic fixes enabled the test, but the result was failing. > > It turns out it was missing a space between the register arguments in > the scan-assembler-times directives. Great find, thanks. > > gcc/testsuite/ChangeLog: > > PR target/119556 > * g

Re: [committed] cobol: Eliminate cobolworx UAT errors when compiling with -Os

Robert Dubner writes: > From e70fe5ed46ab129a8b1da961c47d3fb75b11b988 Mon Sep 17 00:00:00 2001 > From: Bob Dubner mailto:rdub...@symas.com > Date: Fri, 4 Apr 2025 13:48:58 -0400 > Subject: [PATCH] cobol: Eliminate cobolworx UAT errors when compiling with > -Os > > Testcases compiled with -Os were

[PATCH] testsuite: arm: fixup more dg-final syntax

... as Richard E mentioned on the ML. Followup to r15-8956-ge90d6c2639c392. gcc/testsuite/ChangeLog: * gcc.target/arm/short-vfp-1.c: Add whitespace around brace. --- Pushed. gcc/testsuite/gcc.target/arm/short-vfp-1.c | 10 +- 1 file changed, 5 insertions(+), 5 deletions(-) diff

[PATCH 2/6] testsuite: fix dg-bogus typo

The dg-bogus directive here is trying to match -Warray-bounds or -Wstringop-overflow, but it got the casing wrong on the latter. gcc.dg/pr89350.c gets this right. gcc/testsuite/ChangeLog: PR middle-end/93437 * g++.dg/warn/Wstringop-overflow-5.C: Fix -Wstringop-overflow casing. --

[PATCH 2/3] testsuite: fix typos in comments

This fixes some 'scan-tree-dump-times' (vs '-time') typos and one or two others I noticed in passing. gcc/testsuite/ChangeLog: * g++.dg/warn/Winvalid-memory-model.C: Fix typo in comment. * gcc.dg/builtin-dynamic-object-size-19.c: Ditto. * gcc.dg/builtin-object-size-19.c: D

[PATCH 1/3] testsuite: harmless dg-* whitespace fixes

These just fix inconsistent/unusual style to avoid noise when grepping and also people picking up bad habits when they see it (as similar mistakes can be harmful). gcc/testsuite/ChangeLog: * c-c++-common/goacc/pr69916.c: Fix unusual whitespace in dg-*. * g++.old-deja/g++.abi/vtabl

[PATCH 0/3] testsuite: more typo/directive fixes

Pushed. Sam James (3): testsuite: harmless dg-* whitespace fixes testsuite: fix typos in comments testsuite: fix dg-* typos gcc/testsuite/c-c++-common/goacc/pr69916.c| 2 +- gcc/testsuite/g++.dg/warn/Winvalid-memory-model.C | 2 +- gcc/testsuite/g++.old-deja/g++.abi

[PATCH 3/3] testsuite: fix dg-* typos

I have a handful more of these left but those introduce FAILs, while these all introduce new PASSes. libstdc++-v3/ChangeLog: * testsuite/std/format/string_neg.cc: Add missing brace for dg-error. gcc/testsuite/ChangeLog: * gcc.dg/analyzer/fd-datagram-socket.c: Fix 'dg-message' sp

[14.x PATCH] c: Allow bool and enum null pointer constants [PR112556]

From: Joseph Myers As reported in bug 112556, GCC wrongly rejects conversion of null pointer constants with bool or enum type to pointers in convert_for_assignment (assignment, initialization, argument passing, return). Fix the code there to allow BOOLEAN_TYPE and ENUMERAL_TYPE; it already allow

Re: [PATCH] gimple: Don't assert that switch has nondefault cases during lowering [PR120080]

Filip Kastl writes: > Hi, > > bootstrapped and regtested on x86_64 linux. Ok to push? > > Filip Kastl > No testcase? I think pinskia's reduced testcase from the bug should be fine. I can handle adding that later if needed though.

Re: [PATCH] ltmain.in: don't suppress output for PIC compilations

Sam James writes: > When working on xz, I set `-Werror=suggest-attribute=returns_nonnull`, and > the build failed (as I expected it to), but with no visible error from > the compiler. There's a mysterious '>/dev/null 2>&1' on the second line where > lib

Re: [AUTOFDO][AARCH64] Add support for profilebootstrap

Kugan Vivekanandarajah writes: > Add support for autoprofiledbootstrap in aarch64. > This is similar to what is done for i386. Added > gcc/config/aarch64/gcc-auto-profile for aarch64 profile > creation. > > How to run: > configure --with-build-config=bootstrap-lto > make autoprofiledbootstrap > >

Re: [14.x PATCH] c: Allow bool and enum null pointer constants [PR112556]

Joseph Myers writes: > On Wed, 14 May 2025, Sam James wrote: > >> > (cherry picked from commit 3d525fce70fa0ffa0b22af6e213643e1ceca5ab5) >> > --- >> > As discussed on the PR, I feel like this is worth having for 14 as we're >> > asking upstreams to

Re: [14.x PATCH] c: Allow bool and enum null pointer constants [PR112556]

Sam James writes: > From: Joseph Myers > > As reported in bug 112556, GCC wrongly rejects conversion of null > pointer constants with bool or enum type to pointers in > convert_for_assignment (assignment, initialization, argument passing, > return). Fix the code there to allo

Re: [PATCH v25 1/3] c: Add _Countof operator

Alejandro Colomar writes: > [...] > diff --git a/gcc/testsuite/gcc.dg/countof-vla.c > b/gcc/testsuite/gcc.dg/countof-vla.c > new file mode 100644 > index ..cc225df20689 > --- /dev/null > +++ b/gcc/testsuite/gcc.dg/countof-vla.c > @@ -0,0 +1,35 @@ > +/* { dg-do compile } */ > +/* { dg

Re: [PATCH] Add newlib to gitignore

Thomas Schwinge writes: > Hi! > > On 2025-06-02T22:01:44+0530, Arijit Kumar Das > wrote: >>> Umm, I don't think so. I've been building crosses with gcc for decades. >>> It should not be necessary, though it may sometimes be convenient. > > Right. Similarly to how it's, for example, documented

Re: [COMMITTED] Check if constant is a member before returning it.

Andrew MacLeod writes: > There is a bug in irange::set_range_from_bitmask where if the bitmask > indicated the result is a singleton, it would simply return that > singleton.  It never actually checked to see if that singleton was > actually contained in the range, in which case it should return

Re: [PATCH] c++: provide #include hint for missing includes [PR110164]

Eric Gallager via Gcc-patches writes: > On Wed, Jun 14, 2023 at 8:29 PM David Malcolm via Gcc-patches > wrote: >> >> PR c++/110164 notes that in cases where we have a forward decl >> of a std library type such as: >> >> std::array x; >> >> we omit this diagnostic: >> >> error: aggregate ‘std::a

Re: [PATCH] c++: provide #include hint for missing includes [PR110164]

> On 15 Jun 2023, at 12:54, David Malcolm wrote: > > On Thu, 2023-06-15 at 01:43 +0100, Sam James wrote: >> >> Eric Gallager via Gcc-patches writes: >> >>> On Wed, Jun 14, 2023 at 8:29 PM David Malcolm via Gcc-patches >>> wrote: >>>&

Re: [PATCH] Add clang's invalid-noreturn warning flag

Julian Waters via Gcc-patches writes: > Anyone? Please see https://gcc.gnu.org/contribute.html#patches, specifically the "Pinging patches, Getting patches applied" section.

Re: [PATCH] Collect both user and kernel events for autofdo tests and autoprofiledbootstrap

Richard Biener via Gcc-patches writes: > On Fri, Jun 30, 2023 at 7:28 AM Eugene Rozenfeld via Gcc-patches > wrote: >> >> When we collect just user events for autofdo with lbr we get some events >> where branch >> sources are kernel addresses and branch targets are user addresses. Without >>

[PATCH] RISC-V: Avoid calloc() poisoning on musl

config/riscv/genrvv-type-indexer.cc: Add missing include. Signed-off-by: Sam James --- gcc/ChangeLog | 5 + gcc/config/riscv/genrvv-type-indexer.cc | 1 + 2 files changed, 6 insertions(+) diff --git a/gcc/ChangeLog b/gcc/ChangeLog index c9e557ce833..7783b2f4

[PATCH v2] RISC-V: Avoid calloc() poisoning on musl

config/riscv/genrvv-type-indexer.cc: Avoid calloc() poisoning on musl by adding include. v2: fix changelog. Signed-off-by: Sam James --- gcc/ChangeLog | 5 + gcc/config/riscv/genrvv-type-indexer.cc | 1 + 2 files changed, 6 insertions(+) diff --git a

[PATCH v3] gcc: Drop obsolete INCLUDE_PTHREAD_H

This is no longer used since 0a62889c7a155f8ed971860d68870dc9c46bb004, so let's clean it up. gcc/ChangeLog: * system.h: Drop unused INCLUDE_PTHREAD_H. Signed-off-by: Sam James --- gcc/system.h | 4 1 file changed, 4 deletions(-) diff --git a/gcc/system.h b/gcc/system.h

[PATCH v4 1/2] RISC-V: Avoid calloc() poisoning on musl

config/riscv/genrvv-type-indexer.cc: Avoid calloc() poisoning on musl by including earlier. * system.h: Add INCLUDE_SSTREAM. Signed-off-by: Sam James --- gcc/config/riscv/genrvv-type-indexer.cc | 2 +- gcc/system.h| 4 2 files changed, 5 inser

[PATCH v4 2/2] gcc: Drop obsolete INCLUDE_PTHREAD_H

This is no longer used since 0a62889c7a155f8ed971860d68870dc9c46bb004, so let's clean it up. gcc/ChangeLog: * system.h: Drop unused INCLUDE_PTHREAD_H. Signed-off-by: Sam James --- gcc/system.h | 4 1 file changed, 4 deletions(-) diff --git a/gcc/system.h b/gcc/system.h

Re: [PATCH v4 1/2] RISC-V: Avoid calloc() poisoning on musl

Kito Cheng writes: > RISC-V part is ok, and I assume you didn't have write access so I'm > gonna push that since the system.h change also got approved :) > > On Tue, Mar 14, 2023 at 5:07 PM Richard Biener via Gcc-patches > wrote: >> >> On Tue, Mar 14, 2023

Re: [PATCH v4 1/2] RISC-V: Avoid calloc() poisoning on musl

bunch! :) >> >> On Tue, Mar 14, 2023 at 5:07 PM Richard Biener via Gcc-patches >> wrote: >> > >> > On Tue, Mar 14, 2023 at 1:24 AM Sam James via Gcc-patches >> > wrote: >> > > >> > > This fixes errors like: >> > >

Re: [PATCH] Turn on LRA on all targets

"Maciej W. Rozycki" writes: > On Sun, 23 Apr 2023, Segher Boessenkool wrote: > >> > There are extra ICEs in regression testing and code quality is poor; cf. >> > . >> >> Do you have something you can show for this? Maybe i

Re: RFC: Introduce -fhardened to enable security-related flags

Marek Polacek via Gcc-patches writes: > Improving the security of software has been a major trend in the recent > years. Fortunately, GCC offers a wide variety of flags that enable extra > hardening. These flags aren't enabled by default, though. And since > there are a lot of hardening flag

Re: [PATCH] LoongArch: Fix unintentional bash-ism in r14-3665.

Yang Yujie writes: > gcc/ChangeLog: > > * config.gcc: remove non-POSIX syntax "<<<". > --- Thanks, I was just about to report this. > gcc/config.gcc | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/gcc/config.gcc b/gcc/config.gcc > index b2fe7c7ceef..6d4c8becd28

Re: [PATCH] [11/12/13/14 Regression] ABI break in _Hash_node_value_base since GCC 11 [PR 111050]

François Dumont via Gcc-patches writes: > Following confirmation of the fix by TC here is the patch where I'm > simply adding a 'constexpr' on _M_next(). > > Please let me know this ChangeLog entry is correct. I would prefer > this patch to be assigned to 'TC' with me as co-author but I don't >

Re: RFC: Introduce -fhardened to enable security-related flags

Hans-Peter Nilsson via Gcc-patches writes: >> Date: Tue, 29 Aug 2023 15:42:27 -0400 >> From: Marek Polacek via Gcc-patches > >> Surely, there must be no ABI impact, the option cannot cause >> severe performance issues, > >> Currently, -fhardened enables: > ... >> -ftrivial-auto-var-init=zero

Re: RFC: Introduce -fhardened to enable security-related flags

Hans-Peter Nilsson writes: >> From: Sam James >> Date: Sun, 17 Sep 2023 05:00:37 +0100 > >> Hans-Peter Nilsson via Gcc-patches writes: >> >> >> Date: Tue, 29 Aug 2023 15:42:27 -0400 >> >> From: Marek Polacek via Gcc-patches >> >

[PATCH] maintainer-scripts/gcc_release: compress xz in parallel

vailable. So, if a different number of threads is preferred, it's fine to set e.g. -T2, etc. Signed-off-by: Sam James --- maintainer-scripts/gcc_release | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/maintainer-scripts/gcc_release b/maintainer-scripts/gcc_

Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel

> On 8 Nov 2022, at 07:34, Eric Botcazou wrote: > >> I build GCC regularly from the weekly snapshots >> and so the decompression time adds up. > > But is very largely dwarfed by the build time of the compiler, isn't it? > It is. It's no big deal if the patch isn't accepted, it's just ver

Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel

> On 8 Nov 2022, at 07:33, Xi Ruoyao wrote: > > On Tue, 2022-11-08 at 07:14 +0000, Sam James via Gcc-patches wrote: >> 1. This should speed up decompression for folks, as parallel xz >>creates a different archive which can be decompressed in parallel. >> >

Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel

> On 8 Nov 2022, at 07:36, Sam James wrote: > > > >> On 8 Nov 2022, at 07:34, Eric Botcazou wrote: >> >>> I build GCC regularly from the weekly snapshots >>> and so the decompression time adds up. >> >> But is very largely dwarfed by

Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel

> On 8 Nov 2022, at 08:52, Jakub Jelinek wrote: > > On Tue, Nov 08, 2022 at 07:40:02AM +0000, Sam James wrote: >>> On 8 Nov 2022, at 07:33, Xi Ruoyao wrote: >>> I'm wondering if running xz -T0 on different machines (with different >>> core numbers) ma

Re: Announcement: Porting the Docs to Sphinx - tomorrow

> On 8 Nov 2022, at 13:55, Martin Liška wrote: > > Hi. > > Tomorrow in the morning (UTC time), I'm going to migrate the documentation > to Sphinx. The final version of the branch can be seen here: > > $ git fetch origin refs/users/marxin/heads/sphinx-final > $ git co FETCH_HEAD > > URL: http

Re: Announcement: Porting the Docs to Sphinx - tomorrow

> On 9 Nov 2022, at 00:00, Joseph Myers wrote: > > On Tue, 8 Nov 2022, Sam James via Gcc wrote: > >> Yes, please (https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106899) >> even for snapshots? Pretty please? :) > > I think we want snapshots to come out

Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel

> On 8 Nov 2022, at 07:14, Sam James wrote: > > 1. This should speed up decompression for folks, as parallel xz > creates a different archive which can be decompressed in parallel. > > Note that this different method is enabled by default in a new > xz release

Re: [PATCH] maintainer-scripts/gcc_release: compress xz in parallel

> On 8 Nov 2022, at 07:14, Sam James wrote: > > 1. This should speed up decompression for folks, as parallel xz > creates a different archive which can be decompressed in parallel. > > Note that this different method is enabled by default in a new > xz release

Re: [PATCH v5] gcc: Drop obsolete INCLUDE_PTHREAD_H

Jeff Law writes: > On 4/2/23 15:33, Sam James wrote: >> gcc/ChangeLog: >> * system.h: Drop unused INCLUDE_PTHREAD_H. > THanks. I've pushed this to the trunk. Cheers Jeff! > jeff best, sam signature.asc Description: PGP signature

[PATCH] testsuite: Add testcase for sparc ICE [PR105573]

r11-10018-g33914983cf3734c2f8079963ba49fcc117499ef3 fixed PR105312 and added a test case for target/arm but the duplicate PR105573 has a test case for target/sparc that was uncommitted until now. 2023-04-21 Sam James PR tree-optimization/105312 PR target/105573 * gcc

Re: [PATCH] testsuite: Add testcase for sparc ICE [PR105573]

Richard Biener writes: > On Fri, 21 Apr 2023, Sam James wrote: > >> r11-10018-g33914983cf3734c2f8079963ba49fcc117499ef3 fixed PR105312 and added >> a test case for target/arm but the duplicate PR105573 has a test case for >> target/sparc that was uncommitted until now

[PATCH v2] testsuite: Add testcase for sparc ICE [PR105573]

r11-10018-g33914983cf3734c2f8079963ba49fcc117499ef3 fixed PR105312 and added a test case for target/arm but the duplicate PR105573 has a test case for target/sparc that was uncommitted until now. 2023-04-21 Sam James PR tree-optimization/105312 PR target/105573 * gcc

Re: [PATCH] c++: NSDMI instantiation from template context [PR109506]

FWIW, we'd love to be able to backport this to GCC 13 (maybe 12, but no big deal there) in Gentoo so we can continue doing large testing builds with a lot of checking enabled, given this affects Chromium. But it's no big deal if it's too invasive. signature.asc Description: PGP signature

Re: [PATCH v4 2/2] gcc: Drop obsolete INCLUDE_PTHREAD_H (ping)

, Mar 14, 2023 at 8:28 AM juzhe.zh...@rivai.ai > wrote: >> >> Thank you for fixing this. I am not familiar with this. >> This generator code (genrvv-type-indexer.cc) is written by @kito. >> >> Kito ? Can you take a look at this? >> >> >> juzhe.zh.

Re: [PATCH v4 2/2] gcc: Drop obsolete INCLUDE_PTHREAD_H (ping)

Jeff Law writes: > On 4/2/23 14:06, Andrew Pinski wrote: >> On Sun, Apr 2, 2023 at 12:55 PM Jeff Law via Gcc-patches >> wrote: >>> >>> >>> >>> On 3/31/23 12:44, Sam James wrote: >>>> >>>> Kito Cheng writes: >&g

[PATCH v5] gcc: Drop obsolete INCLUDE_PTHREAD_H

e consumer in the tree which is now gone. gcc/ChangeLog: * system.h: Drop unused INCLUDE_PTHREAD_H. Thanks-to: Andrew Pinski Signed-off-by: Sam James --- gcc/system.h | 4 1 file changed, 4 deletions(-) diff --git a/gcc/system.h b/gcc/system.h index cf45db3f97e..3fdad7abf1e 100644

<    1   2   3   4   5