On Tue, 16 Jan 2024, juzhe.zh...@rivai.ai wrote:
> >> That's probably because we have vect_variable_length && vect128 instead?
> Yes. Both RVV and SVE uses 128bit vector SLP.
>
> The optimized IR (both ARM SVE and RVV are similiar):
> vect__1.5_189 = MEM [(int *)x_50(D)];
> vect__1.6_191 =
On Tue, 16 Jan 2024, Juzhe-Zhong wrote:
> Notice there is a regression recently:
> XPASS: gcc.dg/vect/bb-slp-subgroups-3.c -flto -ffat-lto-objects
> scan-tree-dump-times slp2 "optimized: basic block" 2
> XPASS: gcc.dg/vect/bb-slp-subgroups-3.c scan-tree-dump-times slp2 "optimized:
> basic
>> That's probably because we have vect_variable_length && vect128 instead?
Yes. Both RVV and SVE uses 128bit vector SLP.
The optimized IR (both ARM SVE and RVV are similiar):
vect__1.5_189 = MEM [(int *)x_50(D)];
vect__1.6_191 = MEM [(int *)x_50(D) + 16B];
mask__2.7_192 = vect__1.5_189
On Tue, 16 Jan 2024, Juzhe-Zhong wrote:
> Recently notice there is a XPASS in RISC-V:
> XPASS: gcc.dg/vect/bb-slp-43.c -flto -ffat-lto-objects scan-tree-dump-not
> slp2 "vector operands from scalars"
> XPASS: gcc.dg/vect/bb-slp-43.c scan-tree-dump-not slp2 "vector operands from
> scalars"
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113258
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
--- Comment #26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107201
--- Comment #3 from GCC Commits ---
The releases/gcc-13 branch has been updated by Georg-Johann Lay
:
https://gcc.gnu.org/g:3f6efe203484f7fb29c048d024dd8205e9e0f193
commit r13-8227-g3f6efe203484f7fb29c048d024dd8205e9e0f193
Author:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #15 from Richard Biener ---
(In reply to Gaius Mulley from comment #14)
> Ah apologies, is it best that I revert:
>
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;
> h=81d5ca0b9b8431f1bd7a5ec8a2c94f04bb0cf032
>
> happy to do this
On Mon, 15 Jan 2024, Robin Dapp wrote:
> I gave it another shot now by introducing a separate function as
> Richard suggested. It's probably not at the location he intended.
>
> The way I read the discussion there hasn't been any consensus
> on how (or rather where) to properly tackle the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113372
--- Comment #18 from rguenther at suse dot de ---
On Mon, 15 Jan 2024, jakub at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113372
>
> --- Comment #17 from Jakub Jelinek ---
> (In reply to Richard Biener from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108016
--- Comment #2 from JuzheZhong ---
#include
std::pair full_add(unsigned a, unsigned b)
{ return std::make_pair(a + b, a + b < a); }
s=/usr/bin/riscv64-unknown-linux-gnu-as --disable-multilib
--disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-7258-20240115151353-g731444b3c39-checking-yes-rtl-df-extra-riscv64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240115 (experimental) (GCC)
Notice there is a regression recently:
XPASS: gcc.dg/vect/bb-slp-subgroups-3.c -flto -ffat-lto-objects
scan-tree-dump-times slp2 "optimized: basic block" 2
XPASS: gcc.dg/vect/bb-slp-subgroups-3.c scan-tree-dump-times slp2 "optimized:
basic block" 2
Checked on both ARM SVE an RVV:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112919
--- Comment #6 from chenglulu ---
Hi，Ruoyao:
I am testing the spec2006 scores when the parameters 'align-loops',
'align-jumps', 'align-functions', and 'align-labels' are '1', '8', '16', and
'32' respectively.
However, the test was suspended due
Recently notice there is a XPASS in RISC-V:
XPASS: gcc.dg/vect/bb-slp-43.c -flto -ffat-lto-objects scan-tree-dump-not slp2
"vector operands from scalars"
XPASS: gcc.dg/vect/bb-slp-43.c scan-tree-dump-not slp2 "vector operands from
scalars"
And checked both ARM SVE and RVV:
在 2024/1/16 下午2:20, Xi Ruoyao 写道:
On Tue, 2024-01-16 at 14:16 +0800, chenglulu wrote:
在 2024/1/16 下午1:34, Xi Ruoyao 写道:
Ping.
On Fri, 2023-12-15 at 20:56 +0800, Xi Ruoyao wrote:
We don't allow SImode in FCC, so constraint z is never really used
here.
gcc/ChangeLog:
*
On Tue, 2024-01-16 at 14:16 +0800, chenglulu wrote:
>
>
> 在 2024/1/16 下午1:34, Xi Ruoyao 写道:
> > Ping.
> >
> > On Fri, 2023-12-15 at 20:56 +0800, Xi Ruoyao wrote:
> > > We don't allow SImode in FCC, so constraint z is never really used
> > > here.
> > >
> > > gcc/ChangeLog:
> > >
> > > *
在 2024/1/16 下午1:34, Xi Ruoyao 写道:
Ping.
On Fri, 2023-12-15 at 20:56 +0800, Xi Ruoyao wrote:
We don't allow SImode in FCC, so constraint z is never really used
here.
gcc/ChangeLog:
* config/loongarch/loongarch.md (movsi_internal): Remove
constraint z.
---
Bootstrapped and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113415
Andrew Pinski changed:
What|Removed |Added
Summary|ICE: RTL check: expected|ICE: RTL check:
|elt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113415
--- Comment #1 from Andrew Pinski ---
This might fail the same way:
```
void
foo(void)
{
unsigned long bitint0[64];
lab:
__asm__ goto("" : "=r"(bitint0) : : : lab);
}
```
I'm going to check-in this if no objection
Hongyu Wang 于2024年1月9日周二 15:14写道：
>
> Hi,
>
> This patch adds missing description for inline asm behavior and related
> compiler switch for APX.
>
> Ok for gcc-wwwdocs?
>
> ---
> htdocs/gcc-14/changes.html | 6 ++
> 1 file changed, 6 insertions(+)
ion algorithms: zlib zstd
gcc version 14.0.1 20240115 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113414
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
Ping.
On Fri, 2023-12-15 at 20:56 +0800, Xi Ruoyao wrote:
> We don't allow SImode in FCC, so constraint z is never really used
> here.
>
> gcc/ChangeLog:
>
> * config/loongarch/loongarch.md (movsi_internal): Remove
> constraint z.
> ---
>
> Bootstrapped and regtested on
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99913
LIU Hao changed:
What|Removed |Added
CC||lh_mouse at 126 dot com
--- Comment #4 from
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43613
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #9
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113414
Xi Ruoyao changed:
What|Removed |Added
CC||xry111 at gcc dot gnu.org
--- Comment #3
On Tue, 2024-01-16 at 10:57 +0800, chenxiaolong wrote:
> 在 2024-01-15一的 15:50 +0800，Xi Ruoyao写道：
> > On Mon, 2024-01-15 at 15:10 +0800, chenxiaolong wrote:
> > > At 14:42 +0800 on the first day of 2024-01-15, Xi Ruoyao wrote：
> > > > On Mon, 2024-01-15 at 14:32 +0800, YunQiang Su wrote:
> > > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=43613
nightstrike changed:
What|Removed |Added
CC||nightstrike at gmail dot com
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113414
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |INVALID
See Also|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113414
--- Comment #1 from Andrew Pinski ---
>The code should be warned, but it did not.
No that is by design. You need to use -Wformat-signedness for that.
But for the second example, the fix it note is wrong only with
-Wformat-signedness .
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113414
Bug ID: 113414
Summary: Incorrent checking for printf format: does not
distinguish whether the variable is signed or unsigned
Product: gcc
Version: 11.4.0
Status:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113091
--- Comment #9 from GCC Commits ---
The master branch has been updated by Feng Xue :
https://gcc.gnu.org/g:57f611604e8bab67af6c0bcfe6ea88c001408412
commit r14-7272-g57f611604e8bab67af6c0bcfe6ea88c001408412
Author: Feng Xue
Date: Thu Dec 28
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113404
--- Comment #1 from GCC Commits ---
The master branch has been updated by Pan Li :
https://gcc.gnu.org/g:5134d3074ad7a462b4c8e2c0bc904b5ba40b7373
commit r14-7271-g5134d3074ad7a462b4c8e2c0bc904b5ba40b7373
Author: Juzhe-Zhong
Date: Tue Jan
LGTM, the big endian for RISC-V has been there for a while, but we
don't pay enough attention to that, so I think reporting sorry for now
is a very reasonable way :)
On Tue, Jan 16, 2024 at 11:05 AM Juzhe-Zhong wrote:
>
> As PR113404 mentioned: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113404
As PR113404 mentioned: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113404
We have ICE when we enable RVV in big-endian mode:
during RTL pass: expand
a-float-point-dynamic-frm-66.i:2:14: internal compiler error: in to_constant,
at poly-int.h:588
0xab4c2c poly_int<2u, unsigned
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111850
Kewen Lin changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned at
在 2024-01-15一的 15:50 +0800，Xi Ruoyao写道：
> On Mon, 2024-01-15 at 15:10 +0800, chenxiaolong wrote:
> > At 14:42 +0800 on the first day of 2024-01-15, Xi Ruoyao wrote：
> > > On Mon, 2024-01-15 at 14:32 +0800, YunQiang Su wrote:
> > > > Xi Ruoyao wrote at 12:11pm on Monday,
> > > > January
> > > >
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109705
--- Comment #5 from GCC Commits ---
The master branch has been updated by Kewen Lin :
https://gcc.gnu.org/g:39fa71a0882928a25bd170580e3e9e89a69dce36
commit r14-7270-g39fa71a0882928a25bd170580e3e9e89a69dce36
Author: Kewen Lin
Date: Mon Jan
Hi,
As pointed out by the discussion in PR109705, the current
vect_long_mult effective target check on Power is broken.
This patch is to fix it accordingly.
With additional change by adding a guard vect_long_mult
in gcc.dg/vect/pr25413a.c , it's tested well on Power{8,9}
LE & BE (also on Power10
Define LOGICAL_OP_NON_SHORT_CIRCUIT as 0, for a short-circuit branch, use the
short-circuit operation instead of the non-short-circuit operation.
SPEC2017 performance evaluation shows 1% performance improvement for fprate
GEOMEAN and no obvious regression for others. Especially, 526.blender_r
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113413
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113413
Bug ID: 113413
Summary: ATAND(Y,X) is unsupported
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: fortran
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112580
Hans-Peter Nilsson changed:
What|Removed |Added
Status|RESOLVED|REOPENED
Resolution|FIXED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=103524
Bug 103524 depends on bug 112580, which changed state.
Bug 112580 Summary: [14 Regression]: g++.dg/modules/xtreme-header-4_b.C et al;
ICE tree check: expected class 'type', have 'declaration'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112580
In r14-7022-34d339bbd0c1f5b4ad9587e7ae8387c912cb028b I implement pattern
vec_concatz, the reg+reg addressing mode is not supported in
vec_concatz. This patch fixes that.
gcc/ChangeLog:
* config/loongarch/lasx.md (vec_concatz): Fix pattern to
support reg+reg addressing mode.
For below pattern, can be treated as a simple move because floating point
and vector share a common register on loongarch64.
(set (reg/v:SF 32 $f0 [orig:93 res ] [93])
(vec_select:SF (reg:V8SF 32 $f0 [115])
(parallel [
(const_int 0 [0])
])))
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112419
--- Comment #7 from Hans-Peter Nilsson ---
(In reply to Richard Biener from comment #6)
> Fixed. I guess.
Correct; sorry, I should have close it myself after the commit.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
kargl at gcc dot gnu.org changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever confirmed|0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113412
Bug ID: 113412
Summary: ATAN(Y,X) does not check arguments and generates wrong
error message.
Product: gcc
Version: 13.0
Status: UNCONFIRMED
Severity: normal
Hi,
This patch adds const0 move checking for CLEAR_BY_PIECES. The original
vec_duplicate handles duplicates of non-constant inputs. But 0 is a
constant. So even a platform doesn't support vec_duplicate, it could
still do clear by pieces if it supports const0 move by that mode.
The test cases
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111267
--- Comment #10 from Roger Sayle ---
A revised and improved patch has been posted for review at
https://gcc.gnu.org/pipermail/gcc-patches/2024-January/643062.html
This patch resolves PR rtl-optimization/111267 by improving RTL-level
forward propagation. This x86_64 code quality regression was caused
(exposed) by my changes to improve how x86's (TImode) argument passing
is represented at the RTL-level (reducing the use of SUBREGs to catch
more optimization
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111956
--- Comment #14 from Gaius Mulley ---
Ah apologies, is it best that I revert:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;h=81d5ca0b9b8431f1bd7a5ec8a2c94f04bb0cf032
happy to do this in the morning.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113334
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113411
Bug ID: 113411
Summary: ABS*ABS can be simplified to ABS
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords: missed-optimization
Severity: enhancement
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106229
David Malcolm changed:
What|Removed |Added
Resolution|--- |FIXED
Status|UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106358
Bug 106358 depends on bug 106229, which changed state.
Bug 106229 Summary: False positives from -Wanalyzer-tainted-array-index with
unsigned char index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106229
What|Removed
On Mon, 15 Jan 2024, Jonathan Wakely wrote:
> I think I'm happy with this now. It has tests for all the new functions,
> and the performance of the charset alias match algorithm is improved by
> reusing part of .
>
> Tested x86_64-linux.
>
> -- >8 --
>
> This is another C++26 change, approved
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11
--- Comment #3 from David Malcolm ---
Should be fixed on trunk for GCC 14 by the above patch.
Still affects GCC 13 and earlier; keeping open to track backporting.
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-7266-gce27b66d952127.
gcc/analyzer/ChangeLog:
PR analyzer/106229
* analyzer.h (compare_constants): New decl.
*
In particular, accessing the result of *calloc (1, SZ) (if non-NULL)
should be known to be all zeroes.
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-7265-gd235bf2e807c5f.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113410
Andrew Pinski changed:
What|Removed |Added
Keywords||diagnostic, ice-checking
Ever
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106229
--- Comment #1 from GCC Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:ce27b66d952127b7abd0f8cceacb79eb6ecf71db
commit r14-7266-gce27b66d952127b7abd0f8cceacb79eb6ecf71db
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=11
--- Comment #2 from GCC Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:d235bf2e807c5f7e959ca5f3f8d92936801f5b80
commit r14-7265-gd235bf2e807c5f7e959ca5f3f8d92936801f5b80
Author: David Malcolm
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113406
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-01-15
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110065
--- Comment #5 from GCC Commits ---
The trunk branch has been updated by Marek Polacek :
https://gcc.gnu.org/g:a3054489117085c095e480c71b6aaeea9a463c37
commit r14-7264-ga3054489117085c095e480c71b6aaeea9a463c37
Author: Marek Polacek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113360
--- Comment #1 from Marek Polacek ---
The "deducing from brace-enclosed initializer" error is emitted during parsing
from listify. The body of init_list is not potentially-constant (due to
erroneous FOR_COND), so we register_constexpr_fundef
On 1/8/24 10:27, Patrick Palka wrote:
On Mon, 8 Jan 2024, Nathaniel Shead wrote:
On Thu, Jan 04, 2024 at 03:39:15PM -0500, Patrick Palka wrote:
On Sun, 3 Dec 2023, Nathaniel Shead wrote:
The TYPE_DECL_SUPPRESS_DEBUG and DECL_EXTERNAL flags use the same
underlying bit. This is causing
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899
--- Comment #12 from GCC Commits ---
The releases/gcc-12 branch has been updated by Patrick Palka
:
https://gcc.gnu.org/g:6477b3b9c3e5be5dfe549dcb7b3cef2b49e3690c
commit r12-10098-g6477b3b9c3e5be5dfe549dcb7b3cef2b49e3690c
Author: Patrick
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113395
Andrew Pinski changed:
What|Removed |Added
Depends on||45274
--- Comment #4 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113395
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
On 1/9/24 03:52, Jakub Jelinek wrote:
Hi!
The copy attributes is allowed on decls as well as types and even has
checks whether decl (set to *node) is DECL_P or TYPE_P, but for diagnostics
unconditionally uses DECL_SOURCE_LOCATION (decl), which obviously only works
if it applies to a decl.
In
On 1/11/24 01:12, Nathaniel Shead wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu. OK for trunk?
-- >8 --
Currently, thread_locals in header modules cause ICEs. This patch makes
the required changes for them to work successfully.
Functions exported by a module need DECL_CONTEXT to be
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104634
Patrick Palka changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899
--- Comment #11 from GCC Commits ---
The releases/gcc-13 branch has been updated by Patrick Palka
:
https://gcc.gnu.org/g:766ea9da8ccff3786ec5df414046f6b1640e7e01
commit r13-8224-g766ea9da8ccff3786ec5df414046f6b1640e7e01
Author: Patrick Palka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104634
--- Comment #5 from GCC Commits ---
The releases/gcc-13 branch has been updated by Patrick Palka
:
https://gcc.gnu.org/g:854c9b682562b103f60e5f0a823f31df17a97568
commit r13-8225-g854c9b682562b103f60e5f0a823f31df17a97568
Author: Patrick Palka
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113396
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |13.3
On Mon, Jan 15, 2024 at 9:45 PM Jonathan Wakely wrote:
> I think I'm happy with this now. It has tests for all the new functions,
> and the performance of the charset alias match algorithm is improved by
> reusing part of .
>
> Tested x86_64-linux.
Looks good to me. Good work, Jon.
Hello Richard:
On 15/01/24 6:25 pm, Ajit Agarwal wrote:
>
>
> On 15/01/24 6:14 pm, Ajit Agarwal wrote:
>> Hello Richard:
>>
>> On 15/01/24 3:03 pm, Richard Biener wrote:
>>> On Sun, Jan 14, 2024 at 4:29 PM Ajit Agarwal wrote:
Hello All:
This patch add the vecload pass to
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113405
--- Comment #3 from Eddie Nolan ---
Fixed (first two commands were superfluous):
echo "module1 module1.gcm" >> ./module1.cpp.o.modmap
echo "module2 module2.gcm" >> ./module2.cpp.o.modmap
echo "module1 module1.gcm" >> ./module2.cpp.o.modmap
g++
It is time to add myself to DCO section for my quicinc email account.
ChangeLog:
* MAINTAINERS (DCO): Add myself.
Signed-off-by: Andrew Pinski
---
MAINTAINERS | 1 +
1 file changed, 1 insertion(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 882694cc47d..cb5a42501dd 100644
---
On 1/15/24 17:14, Marek Polacek wrote:
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
OK, thanks.
-- >8 --
Here we started crashing with r14-1659 because that removed the
auto checking in cp_parser_template_type_arg which seemed like
dead code. But the attached test shows
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
-- >8 --
Here we started crashing with r14-1659 because that removed the
auto checking in cp_parser_template_type_arg which seemed like
dead code. But the attached test shows that the code can still
be reached because
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104634
--- Comment #3 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:47673571b28278d857371167f4b67a04a1b87b59
commit r14-7261-g47673571b28278d857371167f4b67a04a1b87b59
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104634
Patrick Palka changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot
gnu.org
Evening folks,
Hope you had wonderful holidays.
Gentle ping on this patch.
Have a lovely night!
--
Arsen Arsenović
signature.asc
Description: PGP signature
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899
Patrick Palka changed:
What|Removed |Added
Status|NEW |ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899
Patrick Palka changed:
What|Removed |Added
Summary|[12/13/14 Regression] ICE |[12/13 Regression] ICE in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109899
--- Comment #9 from GCC Commits ---
The master branch has been updated by Patrick Palka :
https://gcc.gnu.org/g:d33c3b5ac9b9b3e314ae9118d483ade7e91a80a5
commit r14-7260-gd33c3b5ac9b9b3e314ae9118d483ade7e91a80a5
Author: Patrick Palka
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113403
Jason Merrill changed:
What|Removed |Added
CC||jason at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113405
--- Comment #2 from Eddie Nolan ---
This series of commands reproduces the issue and does not use CMake:
g++ -g -std=c++20 -E -x c++ ./module2.cpp \
-MT ./module2.cpp.o.ddi -MD -MF ./module2.cpp.o.ddi.d \
-fmodules-ts
On 11 January 2024 10:59:21 CET, YunQiang Su wrote:
>Fix build warning:
> mips.cc: warning: unused parameter 'decl'.
>
>gcc
> * config/mips/mips.cc (mips_start_function_definition):
> Add ATTRIBUTE_UNUSED.
>---
> gcc/config/mips/mips.cc | 3 ++-
> 1 file changed, 2 insertions(+), 1
On 1/15/24 04:41, Nathaniel Shead wrote:
While working on another bug, I noticed the ENABLE_SCOPE_CHECKING macro
and thought to try it out. It caused selftest to ICE. This patch is a
minimal fix to get it working again.
Probably this should use a test to stop this regressing again in the
future
On 1/8/24 13:40, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look
OK for trunk/13/12?
OK.
-- >8 --
The get_target_expr call added in r12-7069-g119cea98f66476 causes us
for the below testcase to call build_vec_delete in a template context,
which builds a
On 1/5/24 11:50, Patrick Palka wrote:
Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look OK
for trunk and perhaps 13?
-- >8 --
invalid_tparm_referent_p was rejecting using the address of a class NTTP
object as a template argument, but this should be fine.
Hmm, I suppose so;
hms: zlib zstd
gcc version 14.0.1 20240115 (experimental) (GCC)
I think I'm happy with this now. It has tests for all the new functions,
and the performance of the charset alias match algorithm is improved by
reusing part of .
Tested x86_64-linux.
-- >8 --
This is another C++26 change, approved in Varna 2022. We require a new
static array of data that is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113313
--- Comment #9 from john.harper at vuw dot ac.nz ---
This variant of my test program (now called test4) hangs with gfortran
but not with other compilers if iam is written to output_unit (like the
original version) or to a file with a different
gcc-trunk//binary-trunk-r14-7255-20240115165927-g6c703b4eb68-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.1 20240115 (experimental) (GCC)
1 - 100 of 334 matches
Mail list logo
