https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115046
--- Comment #1 from 康桓瑋 ---
Oh, maybe this is just because MSVC does not use std::optional but uses
_Defaultabox.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115046
Bug ID: 115046
Summary: meta-recursion when apply join_view with as_const_view
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
And an improvement to using slli.uw...
I recently added the ability to use slli.uw in the synthesis path. That
code was conditional on the right justified constant being a LUI_OPERAND
after sign extending from bit 31 to bit 63.
That code is working fine, but could be improved. Specifically
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #40 from Sam James ---
That came up at https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111600#c29.
LAST_UPDATED: Sat May 11 17:04:43 UTC 2024 (revision r15-384-g1da83fece29)
=== acats tests ===
FAIL: cb1010a
=== acats Summary ===
# of expected passes2327
# of unexpected failures1
Native configuration is s390x-ibm-linux-gnu arch14
Overnight testing showed a small number of cases where constant
synthesis was doing something dumb. Specifically generating more
instructions than the number of bits set in the constant.
It was a minor goof in the recent bseti code. In the code to first
figure out what bits LUI could set, I
On Fri, 10 May 2024, Jason Merrill wrote:
> On 5/9/24 16:23, Patrick Palka wrote:
> > Bootstrapped and regtested on x86_64-pc-linux-gnu, does this look
> > OK for trunk/14? For trunk as a follow-up I can implement the
> > mentionted representation change to use CALL_EXPR instead of
> >
LAST_UPDATED: Sun May 12 00:00:08 UTC 2024 (revision r15-385-gd4974fd2273)
Target is pru-unknown-elf
Host is x86_64-pc-linux-gnu
=== gcc tests ===
Running target pru-sim
FAIL: c-c++-common/analyzer/out-of-bounds-diagram-11.c (test for excess errors)
FAIL:
LAST_UPDATED: Sat May 11 17:25:03 UTC 2024 (revision r15-384-g1da83fece29)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
9 May 2024 6:02:34 pm Peter Damianov :
Since windows 10 release v1511, the windows console has had support for
VT100
escape sequences. We should try to enable this, and utilize it where
possible.
gcc/ChangeLog:
* diagnostic-color.cc (should_colorize): Enable processing of VT100
Currently, commands like:
gcc -o file.c -lm
will delete the user's code.
This patch makes the linker write executables to a temp file, and then renames
the temp file if successful. This fixes the case above, but has limitations.
The source file will still get overwritten if the link "succeeds",
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113882
Andrew Pinski changed:
What|Removed |Added
Ever confirmed|0 |1
Assignee|unassigned at gcc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113880
Andrew Pinski changed:
What|Removed |Added
Last reconfirmed||2024-05-11
Ever confirmed|0
Snapshot gcc-14-20240511 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/14-20240511/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 14 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
LAST_UPDATED: Sat May 11 17:04:43 UTC 2024 (revision r15-384-g1da83fece29)
=== acats tests ===
FAIL: cb1010a
=== acats Summary ===
# of expected passes2327
# of unexpected failures1
Native configuration is s390x-ibm-linux-gnu default
# From
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_eabi-build/657/:
LAST_UPDATED: 2024-05-11T21:06:32+00:00 (master revision
gcc-15-385-gd4974fd2273) arm-eabi
Target is arm-unknown-eabi
Host is arm-unknown-eabi
=== libstdc++ tests ===
Running target qemu
git commit g:d4974fd22730014e337fd7ec2471945ba8afb00e
gcc-descr r15-385-gd4974fd2273001
power8
Linux 5.4.0-177-generic ppc64le
GNU Make 4.2.1
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 18:40:03 UTC 2024
Hi Paul,
Am 11.05.24 um 08:20 schrieb Paul Richard Thomas:
Hi Harald,
Thanks for the review. The attached resubmission fixes all the invalid
accesses, memory leaks and puts right the incorrect result.
In the course of fixing the fix, I found that deferred character length
MOLDs gave an ICE
es ompexp
"__atomic_fetch_add" 1
FAIL: c-c++-common/gomp/atomic-9.c -std=gnu++14 scan-tree-dump-times ompexp
"__atomic_fetch_add" 1
FAIL: c-c++-common/gomp/atomic-9.c -std=gnu++17 scan-tree-dump-times ompexp
"__atomic_fetch_add" 1
FAIL: c-c++-common/gomp/atomic-9.c -std=g
# From
https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-arm-build/1156/:
LAST_UPDATED: 2024-05-11T18:43:02+00:00 (master revision
gcc-15-385-gd4974fd2273) armv8l-unknown-linux-gnueabihf
Native configuration is armv8l-unknown-linux-gnueabihf
=== libatomic tests ===
git commit g:d4974fd22730014e337fd7ec2471945ba8afb00e
gcc-descr r15-385-gd4974fd2273001
power9 BE
Linux 6.7.12-powerpc64 ppc64
GNU Make 4.3
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 17:51:06 UTC 2024
git commit g:d4974fd22730014e337fd7ec2471945ba8afb00e
gcc-descr r15-385-gd4974fd2273001
power9 IEEE128
Linux 6.9.0-0.rc6.52.fc41.ppc64le ppc64le
GNU Make 4.4.1
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11
LAST_UPDATED: Sat May 11 17:55:09 UTC 2024 (revision r15-385-gd4974fd2273)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
Hi Peter,
On Fri, 2024-05-10 at 12:07 +0100, Peter Tribble wrote:
> Tribblix is built from the last commit that worked (November 2021), with any
> relevant changes
> since cherry-picked on top. So in terms of timeline Tribblix is contemporary
> with 11.4, with
> hardware support matching the
git commit g:1da83fece2963cfe0df57ac5e85dd1f92427ca70
gcc-descr r15-384-g1da83fece2963c
power8
Linux 5.4.0-177-generic ppc64le
GNU Make 4.2.1
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 16:33:44 UTC 2024
# From
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m23_eabi-build/378/:
LAST_UPDATED: 2024-05-11T14:34:47+00:00 (master revision
gcc-15-382-ged6690a0ca9) arm-eabi
{-mthumb/-march=armv8-m.base/-mtune=cortex-m23/-mfloat-abi=soft/-mfpu=auto}
Target is arm-unknown-eabi
Host
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110014
Segher Boessenkool changed:
What|Removed |Added
Resolution|FIXED |---
Status|RESOLVED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109577
Segher Boessenkool changed:
What|Removed |Added
CC||segher at gcc dot gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115039
--- Comment #2 from GCC Commits ---
The master branch has been updated by Harald Anlauf :
https://gcc.gnu.org/g:d4974fd22730014e337fd7ec2471945ba8afb00e
commit r15-385-gd4974fd22730014e337fd7ec2471945ba8afb00e
Author: Harald Anlauf
Date:
https://gcc.gnu.org/g:d4974fd22730014e337fd7ec2471945ba8afb00e
commit r15-385-gd4974fd22730014e337fd7ec2471945ba8afb00e
Author: Harald Anlauf
Date: Fri May 10 21:18:03 2024 +0200
Fortran: fix dependency checks for inquiry refs [PR115039]
gcc/fortran/ChangeLog:
PR
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115045
Bug ID: 115045
Summary: views::adjacent_transform<0> is underconstrained
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
git commit g:1da83fece2963cfe0df57ac5e85dd1f92427ca70
gcc-descr r15-384-g1da83fece2963c
power9 BE
Linux 6.7.12-powerpc64 ppc64
GNU Make 4.3
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 16:13:06 UTC 2024
LAST_UPDATED: Sat May 11 15:55:09 UTC 2024 (revision r15-384-g1da83fece29)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
LAST_UPDATED: Sat May 11 10:25:03 UTC 2024 (revision r15-380-g1b0919cd147)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115044
Bug ID: 115044
Summary: -Wanalyzer-malloc-leak diagnostic in terminal path
Product: gcc
Version: 14.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
On Thu, May 9, 2024 at 1:47 PM David Malcolm wrote:
>
> From: Tim Lange
>
> This patch adds the reproducers reported in PR 110014 as test cases. The
> false positives in those cases are already fixed with PR 109577.
>
> 2023-06-09 Tim Lange
>
> PR analyzer/110014
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442
--- Comment #20 from Jonathan Wakely ---
(In reply to Jan Hubicka from comment #19)
> Similar argument can IMO be used for eliding unused memory allocations. It
> is kind of up to std::vector implementation on how many
>
On Thu, May 9, 2024 at 1:45 PM David Malcolm wrote:
>
> From: Tim Lange
>
> Currently, the analyzer tries to prove that the allocation size is a
> multiple of the pointee's type size. This patch reverses the behavior
> to try to prove that the expression is not a multiple of the pointee's
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114990
--- Comment #3 from Patrick Palka ---
I reckon it's not something we can fix/implement in a point release of GCC 14,
but hopefully for 15...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109577
--- Comment #9 from nightstrike ---
(In reply to David Malcolm from comment #8)
> Should be fixed for GCC 13 (for the upcoming GCC 13.3) by the above patches.
Did you miss my comment #5 highlighting the need to adjust the declaration of
malloc
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=110014
--- Comment #6 from nightstrike ---
(In reply to David Malcolm from comment #5)
> Should be fixed for GCC 13 (for the upcoming GCC 13.3) by the above patch.
Did you miss my comment #3 that highlighted the problem due to assuming that
size_t ==
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112728
Iain Sandoe changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109442
--- Comment #19 from Jan Hubicka ---
Note that the testcase from PR115037 also shows that we are not able to
optimize out dead stores to the vector, which is another quite noticeable
problem.
void
test()
{
std::vector test;
LAST_UPDATED: Sat May 11 14:25:09 UTC 2024 (revision r15-383-g1f129e5e2b7)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
# From https://ci.linaro.org/job/tcwg_gcc_check--master-arm-build/2091/:
LAST_UPDATED: 2024-05-11T15:09:21+00:00 (master revision
gcc-15-384-g1da83fece29) armv8l-unknown-linux-gnueabihf
Native configuration is armv8l-unknown-linux-gnueabihf
=== libatomic tests ===
Running
LAST_UPDATED: Sat May 11 08:26:15 UTC 2024 (revision r15-377-g3dab8f8a542)
=== acats tests ===
=== acats Summary ===
# of expected passes2328
# of unexpected failures0
Native configuration is x86_64-pc-linux-gnu
=== gcc tests
Hi,
On some targets it seems that ssize_t is not defined by any of the headers
transitively included by . This leads to a bootstrap fail when jit is
enabled. The attached patch fixes it by include . Other headers in
GCC treat as available on all targets, so we include it
unconditionally.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80182
--- Comment #5 from Peter Damianov ---
I submitted a patch for this:
https://gcc.gnu.org/pipermail/gcc-patches/2024-May/651340.html
Currently, commands like:
gcc -o file.c -lm
will delete the user's code.
This patch makes the linker write executables to a temp file, and then renames
the temp file if successful. This fixes the case above, but has limitations.
The source file will still get overwritten if the link "succeeds",
A passing build has been detected on builder gcc-debian-testing-x86_64 while
building gcc.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/161/builds/10740
Build state: build successful
Revision: 1f129e5e2b74c20a757f2809792af229b551b09b
Worker: bb1-1
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=56556
--- Comment #4 from Gaël Bonithon ---
It would be nice if this could be fixed. I'm currently experimenting with
porting a GTK text editor to Qt6, and it seems that because of this, I can't
name a local variable 'data' in a method of a QWidget
https://gcc.gnu.org/g:1da83fece2963cfe0df57ac5e85dd1f92427ca70
commit r15-384-g1da83fece2963cfe0df57ac5e85dd1f92427ca70
Author: Mark Harmstone
Date: Sat May 11 08:24:59 2024 -0600
[PATCH v4 4/4] Output S_COMPILE3 symbol in CodeView debug section
Outputs the S_COMPILE3 symbol in
https://gcc.gnu.org/g:1f129e5e2b74c20a757f2809792af229b551b09b
commit r15-383-g1f129e5e2b74c20a757f2809792af229b551b09b
Author: Mark Harmstone
Date: Sat May 11 08:19:53 2024 -0600
[PATCH v2 3/4] Output line numbers in CodeView section
Outputs the DEBUG_S_LINES block in the
https://gcc.gnu.org/g:ed6690a0ca911138abd4d707510fd03ef188a28b
commit r15-382-ged6690a0ca911138abd4d707510fd03ef188a28b
Author: Mark Harmstone
Date: Sat May 11 08:15:43 2024 -0600
[PATCH v2 2/4] Output file checksums in CodeView section
Outputs the file name and MD5 hash of the
https://gcc.gnu.org/g:36781ef8fd26eb9a0686957e7bac8f5ccc5ecc3f
commit r15-381-g36781ef8fd26eb9a0686957e7bac8f5ccc5ecc3f
Author: Mark Harmstone
Date: Sat May 11 08:08:50 2024 -0600
[PATCH v2 1/4] Support for CodeView debugging format
This patch and the following add initial
On 10/30/23 6:28 PM, Mark Harmstone wrote:
This patch and the following add initial support for Microsoft's
CodeView debugging format, as used by MSVC, to mingw targets.
Note that you will need a recent version of binutils for this to be
useful. The best way to view the output is to run
git commit g:bfb88b1406cdd8d3f97e280b0d63529aa925f18a
gcc-descr r15-354-gbfb88b1406cdd8
power8
Linux 5.4.0-177-generic ppc64le
GNU Make 4.2.1
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Fri May 10 03:11:28 UTC 2024
git commit g:1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
gcc-descr r15-380-g1b0919cd147a2b
power8
Linux 5.4.0-177-generic ppc64le
GNU Make 4.2.1
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 11:41:16 UTC 2024
# From https://ci.linaro.org/job/tcwg_gcc_check--master-aarch64-build/1980/:
LAST_UPDATED: 2024-05-11T12:56:55+00:00 (master revision
gcc-15-380-g1b0919cd147) aarch64-unknown-linux-gnu
Native configuration is aarch64-unknown-linux-gnu
=== libatomic tests ===
Running target
This patch add a new DF problem, named DF_LIVE_SUBREG. This problem
is extended from the DF_LR problem and support track the subreg liveness
of multireg pseudo if these pseudo satisfy the following conditions:
1. the mode size greater than it's REGMODE_NATURAL_SIZE.
2. the reg is used in
V3: Address comments from Dimitar Dimitrov
These patches are used to add a new data flow DF_LIVE_SUBREG,
which will track subreg liveness and then apply it to IRA and LRA
passes (enabled via -O3 or -ftrack-subreg-liveness). These patches
are for GCC 15. And these codes are pushed to the
This patch apply the DF_LIVE_SUBREG to LRA pass. More changes were made
to the LRA than the IRA since the LRA will modify the DF data directly.
The main big changes are centered on the lra-lives.cc file.
Co-authored-by: Lehua Ding
gcc/ChangeLog:
* lra-coalesce.cc (update_live_info):
This patch simple replace df_get_live_in to df_get_subreg_live_in
and replace df_get_live_out to df_get_subreg_live_out.
Co-authored-by: Lehua Ding
gcc/ChangeLog:
* ira-build.cc (create_bb_allocnos): Apply DF_LIVE_SUBREG data.
(create_loop_allocnos): Diito.
*
Add new flag -ftrack-subreg-liveness to enable track-subreg-liveness.
This flag is enabled at -O3/fast.
Co-authored-by: Lehua Ding
gcc/ChangeLog:
* common.opt: Add -ftrack-subreg-liveness option.
* common.opt.urls: Ditto.
* doc/invoke.texi: Ditto.
* opts.cc:
# From
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_eabi-build/400/:
LAST_UPDATED: 2024-05-11T12:32:04+00:00 (master revision
gcc-15-380-g1b0919cd147) arm-eabi
{-mthumb/-march=armv7-m/-mtune=cortex-m3/-mfloat-abi=softfp/-mfpu=auto}
Target is arm-unknown-eabi
Host is
git commit g:1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
gcc-descr r15-380-g1b0919cd147a2b
power9 IEEE128
Linux 6.9.0-0.rc6.52.fc41.ppc64le ppc64le
GNU Make 4.4.1
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11
git commit g:1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
gcc-descr r15-380-g1b0919cd147a2b
power9 BE
Linux 6.7.12-powerpc64 ppc64
GNU Make 4.3
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 11:24:13 UTC 2024
I wasn't entirely sure what to do with the 'abi/main.C' testcase here;
is this OK, or should I e.g. lower the linkage error to a pedwarn for
the purposes of this test?
Bootstrapped and regtested on x86_64-pc-linux-gnu, and lightly checked
with a MinGW32 cross. OK for trunk?
-- >8 --
This patch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115043
Bug ID: 115043
Summary: aarch64 locally_streaming function appears to have CFA
note on wrong instruction in prologue
Product: gcc
Version: unknown
Status: UNCONFIRMED
LAST_UPDATED: Sat May 11 10:55:09 UTC 2024 (revision r15-380-g1b0919cd147)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=115038
--- Comment #1 from Christoph Reiter ---
Another downstream report with the same error:
https://github.com/msys2/MINGW-packages/issues/20864
I've c-reduced that as well to:
```
// gcc -c -fno-omit-frame-pointer -O2 repro.cpp
struct d {
d();
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=54179
--- Comment #39 from Brjd ---
Let me share what I notice in 14.1. Significant improvement in insn-emit.cc and
gimple-match.cc. This is good news.
Insn-recog.cc is much the same and needs ~ 1.6 GiB RAM. Yet, another possible
issue in the future
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114112
Göran Uddeborg changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
git commit g:18c93c65a9fbaaf3762198e78fb3c24b9b6fd9fc
gcc-descr r15-379-g18c93c65a9fbaa
power8
Linux 5.4.0-177-generic ppc64le
GNU Make 4.2.1
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 09:31:56 UTC 2024
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99798
Mikael Morin changed:
What|Removed |Added
Status|NEW |ASSIGNED
Assignee|unassigned
# From
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-arm_v7a_softfp_eabi-build/466/:
LAST_UPDATED: 2024-05-11T09:27:49+00:00 (master revision
gcc-15-377-g3dab8f8a542) arm-eabi
{-marm/-march=armv7-a/-mfpu=vfpv3-d16/-mfloat-abi=softfp}
Target is arm-unknown-eabi
Host is
git commit g:18c93c65a9fbaaf3762198e78fb3c24b9b6fd9fc
gcc-descr r15-379-g18c93c65a9fbaa
power9 BE
Linux 6.7.12-powerpc64 ppc64
GNU Make 4.3
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11 09:30:27 UTC 2024
git commit g:18c93c65a9fbaaf3762198e78fb3c24b9b6fd9fc
gcc-descr r15-379-g18c93c65a9fbaa
power9 IEEE128
Linux 6.9.0-0.rc6.52.fc41.ppc64le ppc64le
GNU Make 4.4.1
DejaGnu:
DejaGnu version 1.6.3
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat May 11
# From
https://ci.linaro.org/job/tcwg_gnu_native_check_gcc--master-aarch64-build/1120/:
LAST_UPDATED: 2024-05-11T10:02:53+00:00 (master revision
gcc-15-377-g3dab8f8a542) aarch64-unknown-linux-gnu
Native configuration is aarch64-unknown-linux-gnu
=== libatomic tests ===
LAST_UPDATED: Sat May 11 09:25:09 UTC 2024 (revision r15-379-g18c93c65a9f)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
Ping, just wondering if anyone has had a chance to look at the patch series.
Thanks.
Carl
On 4/19/24 14:04, Carl Love wrote:
> GCC maintainers:
>
> The following patch series removes duplicate built-ins. There are patches to
> extend an existing overloaded
LAST_UPDATED: Sat May 11 03:25:03 UTC 2024 (revision r15-377-g3dab8f8a542)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION
Fixed the problems and committed to trunk.
Thanks,
Di Zhao
> -Original Message-
> From: Richard Biener
> Sent: Friday, May 10, 2024 8:56 PM
> To: Di Zhao OS
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] tree-optimization/114760 - check variants of >> and << in
> loop-niter
>
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114760
--- Comment #2 from GCC Commits ---
The master branch has been updated by Di Zhao :
https://gcc.gnu.org/g:1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
commit r15-380-g1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
Author: dzhao.ampere
Date: Fri May
https://gcc.gnu.org/g:1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
commit r15-380-g1b0919cd147a2b6ccdee2b1217bf0200bdcc87aa
Author: dzhao.ampere
Date: Fri May 10 11:55:18 2024 +0800
tree-optimization/114760 - check variants of >> and << in loop-niter
When recognizing bit counting
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985
--- Comment #18 from Aldy Hernandez ---
Ah, it looks like seurer already beat me to the preprocessed source.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114985
--- Comment #17 from Aldy Hernandez ---
(In reply to Martin Jambor from comment #16)
> I'll have look, hopefully on Monday.
Thanks Martin.
To reproduce the problem:
1. Revert this patch:
commit d7bb8eaade3cd3aa70715c8567b4d7b08098e699
I have pushed a few cleanups to make it easier to move forward without
disturbing passes which are affected by IPA's mixing up the range
types. As I explained in my previous patch, this restores the default
behavior of silently returning VARYING when a range operator is
unsupported in either a
For the record, we have always returned false (VARYING) for
unsupported range operators. This patch just restores the behavior
we've always had, while adding a knob for further analysis (for
example. IPA which is getting its range types mixed up).
Aldy
On Sat, May 11, 2024 at 11:28 AM Aldy
The canonical way to indicate that a range operator is unsupported is
to return false, which has the sematic meaning of VARYING. This patch
cleans up a few default virtuals that were trying harder to set
VARYING manually.
gcc/ChangeLog:
* range-op-ptr.cc (range_operator::fold_range):
The trap in the range-op dispatch code is really an internal debugging
aid, and only a temporary one for a few weeks while the dust settles.
This patch turns it off by default, allowing problematic passes to
turn it on for analysis.
gcc/ChangeLog:
* range-op.cc
https://gcc.gnu.org/g:18c93c65a9fbaaf3762198e78fb3c24b9b6fd9fc
commit r15-379-g18c93c65a9fbaaf3762198e78fb3c24b9b6fd9fc
Author: Aldy Hernandez
Date: Fri May 10 18:55:34 2024 +0200
[prange] Default unimplemented prange operators to false.
The canonical way to indicate that a range
https://gcc.gnu.org/g:45ef24f2702dac4f8707ca682ed364019ee90c44
commit r15-378-g45ef24f2702dac4f8707ca682ed364019ee90c44
Author: Aldy Hernandez
Date: Fri May 10 23:21:29 2024 +0200
[prange] Do not trap by default on range dispatch mismatches.
The trap in the range-op dispatch code
# From
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m3_softfp_eabi-build/15/:
LAST_UPDATED: 2024-05-11T08:40:03+00:00 (master revision
gcc-15-377-g3dab8f8a542) arm-eabi
{-mthumb/-march=armv7-m/-mtune=cortex-m3/-mfloat-abi=softfp/-mfpu=auto}
Target is arm-unknown-eabi
Host
# From
https://ci.linaro.org/job/tcwg_gnu_embed_check_gcc--master-thumb_m55_hard_eabi-build/393/:
LAST_UPDATED: 2024-05-11T07:59:47+00:00 (master revision
gcc-15-377-g3dab8f8a542) arm-eabi
{-mthumb/-march=armv8.1-m.main+mve.fp+fp.dp/-mtune=cortex-m55/-mfloat-abi=hard/-mfpu=auto}
Target is
This patch optimizes the compilation performance of std::decay
by dispatching to the new __decay built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (decay): Use __decay built-in trait.
Signed-off-by: Ken Matsui
---
libstdc++-v3/include/std/type_traits | 6 ++
1 file
This patch optimizes the compilation performance of
std::add_rvalue_reference by dispatching to the new
__add_rvalue_reference built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (add_rvalue_reference): Use
__add_rvalue_reference built-in trait.
This patch optimizes the compilation performance of std::remove_extent
by dispatching to the new __remove_extent built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (remove_extent): Use __remove_extent
built-in trait.
Signed-off-by: Ken Matsui
---
This patch optimizes the compilation performance of
std::remove_all_extents by dispatching to the new
__remove_all_extents built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (remove_all_extents): Use
__remove_all_extents built-in trait.
Signed-off-by: Ken Matsui
This patch optimizes the compilation performance of std::add_pointer
by dispatching to the new __add_pointer built-in trait.
libstdc++-v3/ChangeLog:
* include/std/type_traits (add_pointer): Use __add_pointer
built-in trait.
Signed-off-by: Ken Matsui
---
1 - 100 of 120 matches
Mail list logo
