https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112715
--- Comment #1 from David Mazières ---
I should have mentioned, I hereby place the test case in the public domain.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112715
Bug ID: 112715
Summary: Incorrect handling of template type aliases
instantiated from decltype of lambdas
Product: gcc
Version: 13.2.1
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112714
Bug ID: 112714
Summary: gcc.dg/tree-ssa/predcom-2.c fails on aarch64-* with
-march=armv9-a+sve
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Keywords:
On Wed, Nov 22, 2023 at 4:18 PM Jeff Law wrote:
>
>
>
> On 11/21/23 16:27, Palmer Dabbelt wrote:
> > The vectorizer picks up these loops and disables unrolling on targets
> > with variable vector factors. That result in better code here, but it
> > trips up the unrolling tests. So just disable
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112531
Andrew Pinski changed:
What|Removed |Added
Target|riscv |riscv aarch64-*-*
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112691
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112691
--- Comment #1 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:bd7f16b43e2afe5bd8429479485b5c70cedbdee6
commit r14-5850-gbd7f16b43e2afe5bd8429479485b5c70cedbdee6
Author: Andrew Pinski
Date:
r14-5628-g53ba8d669550d3 added noipa to f1 but `-fno-ipa-vrp` should have been
used
instead. The testcase is testing about the clone of f1 so turning off
IPA VRP is the correct approach here rather than turning off of IPA on the
function.
gcc/testsuite/ChangeLog:
PR testsuite/112691
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112688
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112688
--- Comment #4 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:a9693bff396b28748464630e4c524776bce3ff4e
commit r14-5849-ga9693bff396b28748464630e4c524776bce3ff4e
Author: Andrew Pinski
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108321
Andrew Pinski changed:
What|Removed |Added
Target Milestone|--- |14.0
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108321
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:6e15e4e1abed02443a27a69455f4bfa49457c99e
commit r14-5848-g6e15e4e1abed02443a27a69455f4bfa49457c99e
Author: Andrew Pinski
Date:
Just like the patch against gcc.target/aarch64/movk.c, the issue here
is the two functions, foo32 and foo64 needed to mark as noipa so that
IPA-VRP cannot propagate the return value.
gcc/testsuite/ChangeLog:
* gcc.target/aarch64/simd/vmulx.x (foo32): Mark as noipa rather
than
Since contracts-tmpl-spec2.C is just testing contracts, I thought it would be
better
to just add `-fsigned-char` to the options rather than change the testcase to
support
both cases.
Committed after testing on aarch64-linux-gnu.
gcc/testsuite/ChangeLog:
PR testsuite/108321
*
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112708
--- Comment #6 from Bruno Haible ---
For comparison, what clang 17 with -fsanitize=address does in this situation,
is to not generate a stepping point at the function entry (xg-message.c:50).
The gdb 'step' command brings me directly to the
Hi Jonathan,
Is there a way I can see my patch merged (when it gets merged)?
Particularly, I want to have a link for the commit. I would like to add
this as "impact on third party software" for the software
https://github.com/tlapack/tlapack.
Thanks,
Weslley
On Mon, Nov 6, 2023 at 3:44 AM
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112443
Sam James changed:
What|Removed |Added
CC||sjames at gcc dot gnu.org
Fix typo. Committed.
gcc/ChangeLog:
* config/riscv/riscv-avlprop.cc (alv_can_be_propagated_p): Fix typo.
(avl_can_be_propagated_p): Ditto.
(vlmax_ta_p): Ditto.
---
gcc/config/riscv/riscv-avlprop.cc | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112713
Bug ID: 112713
Summary: RISC-V: Trunk GCC regression on VSETVL PASS comparing
with GCC-13
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
e
>> is clean?
>
> I was able to build a native GCC:
>
> /tmp/sh/i-native/bin/gcc --version --verbose
> Using built-in specs.
> COLLECT_AS_OPTIONS='--version'
> COLLECT_GCC=/tmp/sh/i-native/bin/gcc
> COLLECT_LTO_WRAPPER=/tmp/sh/i-native/lib/gcc/x86_64-pc-linux-gnu/
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112712
Bug ID: 112712
Summary: Crash when compiling g++ -m68020-60 -O2
Product: gcc
Version: 13.2.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c++
I don't think so, I'm concerned that it might eat the xobj parameter if
we do it that way. Besides, all we want is the lambda type anyway, I
don't want to build a whole new node just to do that. Upon further
consideration I think my solution does work and shouldn't cause
problems. The field that
Snapshot gcc-13-20231125 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/13-20231125/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 13 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #13 from Alex Henrie ---
I should clarify that I was testing with GCC 12.2. It turns out that GCC 12.3
does not crash, and I have now confirmed that the patch from comment #5 applied
to GCC 12.3 fixes
-in specs.
COLLECT_AS_OPTIONS='--version'
COLLECT_GCC=/tmp/sh/i-native/bin/gcc
COLLECT_LTO_WRAPPER=/tmp/sh/i-native/lib/gcc/x86_64-pc-linux-gnu/14.0.0/lto-wrapper
gcc (GCC) 14.0.0 20231125 (experimental) [master 9c26c91b94e]
Copyright (C) 2023 Free Software Foundation, Inc.
This is free software; see
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112688
--- Comment #3 from Andrew Pinski ---
movk.c is fixed, I will submit the change for vmulxd_*_2.c in a few.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112688
--- Comment #2 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:8d559a9b85d9a6de4f358171178a74605f554082
commit r14-5845-g8d559a9b85d9a6de4f358171178a74605f554082
Author: Andrew Pinski
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
--- Comment #3 from Sergei Trofimovich ---
I confirm bisect landed on r14-5831-gaae723d360ca26 as well.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112711
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2023-11-25
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112709
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Summary|address
LTO compression algorithms: zlib
gcc version 14.0.0 20231125 (experimental) (GCC)
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #12 from Alex Henrie ---
Created attachment 56687
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=56687=edit
Minimal example to reproduce the crash
Here's a minimal example that crashes on MinGW 12 with -m32 -mavx512f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106856
--- Comment #19 from anlauf at gcc dot gnu.org ---
*** Bug 96655 has been marked as a duplicate of this bug. ***
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96655
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Resolution|--- |DUPLICATE
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
anlauf at gcc dot gnu.org changed:
What|Removed |Added
CC||anlauf at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #11 from Alex Henrie ---
Well, this is interesting: Unpatched MinGW 12 crashes in the same way if I set
both -march=native and -mpreferred-stack-boundary=2. So the problem is not the
patch itself, it's just that the patch revealed
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
--- Comment #10 from Gabriel Ivăncescu ---
(In reply to Alexander Monakov from comment #9)
> -mpreferred-stack-boundary=n means that functions consume stack in
> increments of 2**n. This is sufficient to ensure that once stack is aligned
> to
On 11/24/23 01:49, waffl3x wrote:
and this in tsubst_lambda_expr that assumes iobj:
/* Fix the type of 'this'. */
fntype = build_memfn_type (fntype, type,
type_memfn_quals (fntype),
type_memfn_rqual (fntype));
Unfortunately, putting a condition on this had some unforeseen
consequences. I've
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112443
--- Comment #8 from Mikael Pettersson ---
Can this be closed now?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112701
--- Comment #2 from Mikael Pettersson ---
gcc-2.95.3 generates neither, gcc-3.0.4 and up generate the bar: .long 0 (or
.zero 4) one.
MicroBlaze is now with AMD, spelt MicroBlaze not MicroBlace, and the
docs have a new address.
---
htdocs/readings.html | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/htdocs/readings.html b/htdocs/readings.html
index 2e320945..e4e68909 100644
--- a/htdocs/readings.html
Refer to the overall project as GCC.
Pushed.
Gerald
---
htdocs/gcc-13/porting_to.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/gcc-13/porting_to.html b/htdocs/gcc-13/porting_to.html
index db0bf2fa..c727d66f 100644
--- a/htdocs/gcc-13/porting_to.html
+++
On Fri, 21 Oct 2022, Joseph Myers wrote:
> C2x allows function prototypes to be given as (...), a prototype
> meaning a variable-argument function with no named arguments.
I noticed this did not make it into gcc-13/changes.html ? Was that
intentional?
Gerald
On Sat, Nov 25, 2023 at 12:26 PM Sebastian Huber
wrote:
>
> contrib/ChangeLog
Did you verify an in-tree build with these works and the testsuite
is clean?
> * download_prerequisites: Update to gmp-6.3.0, mpfr-4.2.1,
> mpc-1.3.1, isl-0.26, and gettext-0.22.4.
> *
The following invoke signed integer overflow (UB) [1]:
month + months{MAX} // where MAX is the maximum value of months::rep
month + months{MIN} // where MIN is the maximum value of months::rep
month - months{MIN} // where MIN is the minimum value of months::rep
weekday + days {MAX}
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110062
--- Comment #11 from Jan Hubicka ---
trunk -O3 -flto -march=native -fopenmp
Operation: Sharpen:
257
256
256
Average: 256 Iterations Per Minute
GCC13 -O3 -flto -march=native -fopenmp
257
256
Gerald Pfeifer wrote:
On Fri, 24 Nov 2023, Tobias Burnus wrote:
While I expect more changes, I want to cleanup my stashed changes.
Good approach!
+ The destory now optionally accepts the depend object as
+ argument.
Is "depend object" a well known technical term in that context?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109811
--- Comment #18 from Jan Hubicka ---
I made a typo:
Mainline with -O2 -flto -march=native run manually since build machinery patch
is needed
23.03
22.85
23.04
Should be
Mainline with -O3 -flto -march=native run
gcc:
PR other/69374
* doc/install.texi (Downloading the source): Sort the list of
front ends and add D, Go, and Modula-2.
---
gcc/doc/install.texi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/gcc/doc/install.texi b/gcc/doc/install.texi
index
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69374
--- Comment #3 from CVS Commits ---
The trunk branch has been updated by Gerald Pfeifer :
https://gcc.gnu.org/g:9c26c91b94eb72397a4892b28022070a33636492
commit r14-5844-g9c26c91b94eb72397a4892b28022070a33636492
Author: Gerald Pfeifer
Date:
FreeBSD 6 and 7 have been end of life for years as have been GCC 4.x
releases, so no point in detailing specifics of changes around those.
gcc:
PR target/69374
* doc/install.texi (Specific) <*-*-freebsd*>: Remove older
contents referencing GCC 4.x.
---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69374
--- Comment #2 from CVS Commits ---
The trunk branch has been updated by Gerald Pfeifer :
https://gcc.gnu.org/g:f7df9d7aca6b7978ad4c08ee24267787a805a301
commit r14-5843-gf7df9d7aca6b7978ad4c08ee24267787a805a301
Author: Gerald Pfeifer
Date:
On Sat, Nov 25, 2023 at 12:03:56PM +, Tamar Christina wrote:
> For the C99 versions of copysign, expand_COPYSIGN has optimized expansions
> inplace.
> One of the hooks there forces it to abs/neg. There is also code in place
> for if the target
> prefers integer expansion over floating
> -Original Message-
> From: Xi Ruoyao
> Sent: Saturday, November 25, 2023 10:43 AM
> To: Jakub Jelinek ; Segher Boessenkool
> ; David Edelsohn
> Cc: gcc-patches@gcc.gnu.org; Tamar Christina ;
> Andrew Pinski
> Subject: Re: [PATCH] rs6000: Canonicalize copysign (x, -1) back to -abs (x)
-pc-linux-gnu-as --disable-libstdcxx-pch
--prefix=/repo/gcc-trunk//binary-trunk-r14-5841-20231125103155-g9866c98e101-checking-yes-rtl-df-extra-nobootstrap-amd64
Thread model: posix
Supported LTO compression algorithms: zlib zstd
gcc version 14.0.0 20231125 (experimental) (GCC)
On Mon, 17 Jul 2023, Haochen Jiang via Gcc-patches wrote:
>GCC now supports the Intel CPU named Granite Rapids through
> -march=graniterapids.
> +The switch enables the AMX-FP16, PREFETCHI ISA extensions.
Do I understand correclty that it enables AMX-FP16 and PREFETCHI?
How about
contrib/ChangeLog
* download_prerequisites: Update to gmp-6.3.0, mpfr-4.2.1,
mpc-1.3.1, isl-0.26, and gettext-0.22.4.
* prerequisites.md5: Update hash.
* prerequisites.sha512: Likewise.
---
contrib/download_prerequisites | 10 +-
contrib/prerequisites.md5
On Fri, 24 Nov 2023, Tobias Burnus wrote:
> Stumbled over this.
Same here. :-)
> Comments?
Thank you for fixing this.
Gerald
http->https it is, once again.
Gerald
gcc:
* doc/standards.texi (Standards): Update ISO C++ reference.
---
gcc/doc/standards.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/gcc/doc/standards.texi b/gcc/doc/standards.texi
index 6eebb9426f3..4b18fa91289 100644
On Sat, 2023-11-25 at 11:17 +0100, Jakub Jelinek wrote:
> The middle-end has been changed quite recently to canonicalize
> -abs (x) to copysign (x, -1) rather than the other way around.
> While I agree with that at GIMPLE level, since it matches the GIMPLE
> goal of as few operations as possible
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109812
liuhongt at gcc dot gnu.org changed:
What|Removed |Added
CC||liuhongt at gcc dot
Hi!
The middle-end has been changed quite recently to canonicalize
-abs (x) to copysign (x, -1) rather than the other way around.
While I agree with that at GIMPLE level, since it matches the GIMPLE
goal of as few operations as possible for a canonical form (-abs (x)
is 2 GIMPLE statements,
Andrew Pinski writes:
> This fixes the testcase.
>
> gcc/testsuite/ChangeLog:
>
> * gcc.target/aarch64/movk.c: Add noipa on dummy_number_generator
> and remove -fno-inline option.
>
> Signed-off-by: Andrew Pinski
OK, thanks.
Richard
> ---
> gcc/testsuite/gcc.target/aarch64/movk.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100651
Francois-Xavier Coudert changed:
What|Removed |Added
CC||fxcoudert at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110334
Eric Gallager changed:
What|Removed |Added
CC||egallager at gcc dot gnu.org
---
This is the original patch and a follow-up to fix an embarrassing markup
mistake.
Gerald
commit 17418f262b17680a07a4493631aa0743b5fe9780
Author: Gerald Pfeifer
Date: Fri Nov 24 09:33:26 2023 +0100
readings: Update OpenPOWER link
The original link now redirects to a very
There are many places in GCC where alternative local sequences are
tried in order to determine what is the cheapest or best alternative
to use in the current target. When any of these sequences involve a
libcall, the current implementation of emit_library_call_value_1
introduce a side-effect
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111408
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109977
Jakub Jelinek changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111408
--- Comment #5 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:9866c98e1015d98b8fc346d7cf73a0070cce5f69
commit r14-5841-g9866c98e1015d98b8fc346d7cf73a0070cce5f69
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109977
--- Comment #6 from CVS Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:a6a43a3b763816fec7c4eec6ae7be5b263dff340
commit r14-5840-ga6a43a3b763816fec7c4eec6ae7be5b263dff340
Author: Jakub Jelinek
Date:
On Sat, Nov 25, 2023 at 8:19 AM Jakub Jelinek wrote:
>
> Hi!
>
> The following testcase is miscompiled in GCC 14 because the
> *jcc_bt_mask and *jcc_bt_mask_1 patterns have just
> one argument in (match_operator 0 "bt_comparison_operator" [...])
> but as bt_comparison_operator is eq,ne, we need
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=07
Alexander Monakov changed:
What|Removed |Added
CC||amonakov at gcc dot gnu.org
---
Come back to review the codes of gather/scatter, notice
gather_scatter_valid_offset_mode_p looks odd.
gather_scatter_valid_offset_mode_p is supposed to block vluxei64/vsuxei64 in
RV32 system.
However, it failed to do that since it is passing data_mode instead of index
mode:
75 matches
Mail list logo
