5241
# of unsupported tests 23143
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240411
(experimental) [master r14-9926-g33f83d3cd8] (GCC)
=== gcc tests ===
Running target unix/-m32
XPASS: gcc.dg/guality/example.c -O0 execution test
A restored build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2466
Build state: build successful
Revision: 671517fc2e28d7b3f8caa2d2d1b26365285d3d99
Worker: bbo2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2480
Build state: build successful
Revision: 90f6b7b56b027c229b519a17ed4bda180b54883d
Worker: bb1-2
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
Bug ID: 114699
Summary: gcc-go -buildmode=c-shared doesn't use -Wl,-z,nodelete
so libraries crash when dlclosed
Product: gcc
Version: 14.0
Status: UNCONFIRMED
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2523
Build state: build successful
Revision: 578068682130e6a438ef2c43692a51415fa1e6b1
Worker: bb1-2
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
--- Comment #3 from Richard W.M. Jones ---
(Edit comment 2: To be clear, that wasn't the thread where the
segfault occurred, which was some golang thread, that was the
thread that was unmapping the memory at the same time. Using
nodelete
# of expected passes178360
# of unexpected failures128
# of unexpected successes 13
# of expected failures 1595
# of unsupported tests 5017
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240411
(experimental) [remote
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2544
Build state: build successful
Revision: 0da798e3666af22ebdf58d39198acff1de71a33b
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2540
Build state: build successful
Revision: 75763b4c50e6d1ffb8cae6d34d5ffd40add1f8d4
Worker: bb2-2
Build
fkdb\\t%v[0-9]*,%v[0-9]*\\n\\t[^:]+\\tlocghil\\t%r2,1
FAIL: gcc.target/s390/vector/vec-scalar-cmp-1.c scan-assembler
ne:\\n[^:]*\\twfcdb\\t%v[0-9]*,%v[0-9]*\\n\\t[^:]+\\tlocghine\\t%r2,1
XPASS: gcc.target/s390/vxe/popcount-1.c scan-assembler vpopctb\\t%v24,%v24
XPASS: gcc.target/s390/vxe/popcount-1.c scan-ass
On 4/11/24 14:02, David Faust wrote:
This patch fixes a small error that could occur in the debug comment
when emitting a type reference with btf_asm_type_ref.
While working on a previous patch, I noticed the following in the asm
output for the test btf-bitfields-4.c:
...
.long
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2561
Build state: build successful
Revision: 1b1f8d898857b69b98095fc26b4dd95bafffdc18
Worker: bb1-1
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2563
Build state: build successful
Revision: ad4c18174bb3dab443435fe19ca593206f98cddf
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2560
Build state: build successful
Revision: 6bed91c311e0fbfc72ad4de605335900fc98a5e6
Worker: bbo2
Build
> -Original Message-
> From: Richard Biener
> Sent: Thursday, April 11, 2024 2:31 AM
> To: Andrew Pinski (QUIC)
> Cc: gcc-patches@gcc.gnu.org
> Subject: Re: [PATCH] match: Fix `!a?b:c` and `a?~t:t` patterns for signed 1
> bit
> types [PR114666]
>
> On Thu, Apr 11, 2024 at 10:43 AM
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2581
Build state: build successful
Revision: e99e565e0aa866cdec407f851d651096fb190f7f
Worker: bbo1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2624
Build state: build successful
Revision: c016d443b814a49fa1f91a08bed12577885f40d9
Worker: bb1-1
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698
Peter Bergner changed:
What|Removed |Added
Component|target |ipa
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698
--- Comment #7 from Andrew Pinski ---
See https://github.com/archiecobbs/libnbcompat/issues/4 for the full analysis
of the issue with sha2.c and even mentions it is shared with many projects.
2079
# of unexpected failures170
# of unexpected successes 14
# of expected failures 1468
# of unsupported tests 3885
/home/gccbuild/build/nightly/build-gcc-12/gcc/xgcc version 12.3.1 20240411
[remotes/origin/releases/gcc-12 r12-10319-gd37be5c041] (GCC)
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2476
Build state: build successful
Revision: 0cecd8278901c32b0326f32105f63ed481bae0c9
Worker: bbo2
Build
[Changes from v1: use btf_dmd_representable_bitfield_p in
btf_asm_sou_member, instead of a slightly incorrect equivalent check.]
This patch fixes an issue with mangled BTF that could occur when
a struct type contains a bitfield member which cannot be represented
in BTF. It is undefined what
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97304
Andrew Pinski changed:
What|Removed |Added
Component|target |driver
--- Comment #16 from Andrew
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114678
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
CC|
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2509
Build state: build successful
Revision: 85201f34877639599c6f53575791d9a6ef66a02b
Worker: bb1-1
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2529
Build state: build successful
Revision: 7b6c52cf4ef53d4f4816cbcd7e086daa1c872d29
Worker: bb1-1
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2536
Build state: build successful
Revision: 8b089cb58ad94ccd14347c27d36408cac2c73de0
Worker: bb1-2
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101865
Peter Bergner changed:
What|Removed |Added
URL|https://gcc.gnu.org/piperma |https://gcc.gnu.org/piperma
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2567
Build state: build successful
Revision: 7e74b450d24074519c8c93dc55c507931b329c5a
Worker: bb1-1
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114695
--- Comment #2 from Andrew Pinski ---
Note you don't need the extra template int argument either to reproduce the
failure:
```
template struct Bar {
void accept(X value) { }
};
template struct Foo;
template
struct Foo...> : Bar... {
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106211
Andrew Pinski changed:
What|Removed |Added
Keywords||c++-lambda
This patch series fixes a few issues with exported using-declarations that have
come up recently.
I was hoping to fix PR114683 and PR114685 as well, but the issues there look to
be much more involved and I'm not yet sure how to handle them. They're
ultimately caused by using-declarations just
This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "gcc-wwwdocs".
The branch, master has been updated
via 9e32f911b70a8c2303b9b60679ce337896ccffdd (commit)
from
This patch fixes an issue with mangled BTF that could occur when
a struct type contains a bitfield member which cannot be represented
in BTF. It is undefined what should happen in such cases, but we can
at least do something reasonable.
Commit
936dd627cd9 "btf: do not skip members of data
On 4/11/24 13:40, Indu Bhagat wrote:
> On 4/11/24 11:53, David Faust wrote:
>> This patch fixes an issue with mangled BTF that could occur when
>> a struct type contains a bitfield member which cannot be represented
>> in BTF. It is undefined what should happen in such cases, but we can
>> at
t;__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=gnu++20 s
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2503
Build state: build successful
Revision: 1083826a89e22c736a80ed93ba9c10c426cff59d
Worker: bb1-1
Build
A retry build has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2502
Build state: worker not available
Revision: (unknown)
Worker: bb2-2
Build Reason: (unknown)
Blamelist:
On 4/11/2024 5:45 AM, Li, Pan2 wrote:
Thanks for reporting this. Just take a look from my test log that 930623-1.c is
all pass.
Thus I bet this difference comes from the build option --with-arch=rv32imac but
my test script take rv64gcv.
I've built the git revision f3fdcf4a37a with
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2527
Build state: build successful
Revision: e5f3ad0fa1955dc83b59d46a92a76507ee3855a2
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2543
Build state: build successful
Revision: ffadba42b3022855db48bdd94e0c95a8480bc278
Worker: bbo2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2539
Build state: build successful
Revision: 0830ce0813e8fcac793b210ce2715712b109ce2c
Worker: bb2-1
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=94630
Michael Meissner changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2572
Build state: build successful
Revision: 37451ad09f7edc081700909208f90b9eea1eb592
Worker: bb2-2
Build
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
The modules code currently neglects to set OVL_USING_P on the dependency
created for a using-decl, which causes it not to remember that the
OVL_EXPORT_P flag had been set on it when emitted from the primary
interface unit.
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
A typo in r14-6978 made us emit too many things. This ensures that we
don't emit using-declarations from the GMF that we don't need to.
PR c++/114600
gcc/cp/ChangeLog:
* module.cc
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2599
Build state: build successful
Revision: c0763eac05f6e8adf05a1d94fc80ded1a9e14f2c
Worker: bb2-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2607
Build state: build successful
Revision: ff773b9030e443dbea0b4357bd10b480ff39c987
Worker: bb1-1
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2609
Build state: build successful
Revision: 55a3049525498a4c06e47c21c15f6b3d6eb1be29
Worker: bb1-2
Build
/nightly/build-gcc-13/gcc/xg++ version 13.2.1 20240411
[releases/gcc-13 r13-8599-g5824e67591] (GCC)
=== gcc tests ===
Running target unix/-m32
XPASS: gcc.dg/guality/example.c -O0 execution test
XPASS: gcc.dg/guality/example.c -O1 -DPREVENT_OPTIMIZATION execution test
XPASS
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114697
Bug ID: 114697
Summary: [DR 233] references in user defined conversions
Product: gcc
Version: unknown
Status: UNCONFIRMED
Severity: normal
Priority: P3
# of expected passes178360
# of unexpected failures128
# of unexpected successes 13
# of expected failures 1595
# of unsupported tests 5017
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240411
(experimental) [remote
Hi!
On 2024-04-11T19:52:51+0200, Martin Jambor wrote:
> contrib/check-params-in-docs.py is a script that checks that all
> options reported with ./gcc/xgcc -Bgcc --help=param are in
> gcc/doc/invoke.texi and vice versa.
Eh, first time I'm hearing about this one!
(a) Shouldn't this be running
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698
--- Comment #3 from Andrew Pinski ---
uint8_t buffer[SHA256_BLOCK_LENGTH];
W256 = (sha2_word32*)context->buffer;
This is starting to smell like the code is violating strict aliasing rules ...
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698
--- Comment #8 from Peter Bergner ---
(In reply to Andrew Pinski from comment #6)
> Note this implementation of sha2.c is shared all over the place it seems and
> has this known issue ...
(In reply to Andrew Pinski from comment #4)
> (In reply
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114698
Peter Bergner changed:
What|Removed |Added
Status|WAITING |RESOLVED
Resolution|---
A restored build has been detected on builder gccrust-debian-i386 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/27/builds/2167
Build state: build successful
Revision: 2163af71247b99e8fd707e5d6da83d14456e02a5
Worker: debian-i386-2
Regressions on master at commit r14-9913 vs commit r14-9894 on Linux/i686
New failures:
FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 21 x == 10 - i
FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin
/git/gcc-test-master-ia32/bld/gcc/xgcc version 14.0.1
20240411 (experimental) [master-ia32 r14-9913-g467898d513e] (GCC)
=== gfortran tests ===
Running target unix
=== gfortran Summary ===
# of expected passes69619
# of expected failures
Regressions on master at commit r14-9913 vs commit r14-9894 on Linux/i686
New failures:
FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects -DPREVENT_OPTIMIZATION line 21 x == 10 - i
FAIL: gcc.dg/guality/pr54693-2.c -O2 -flto -fuse-linker-plugin
ted tests 4111
/export/gnu/import/git/gcc-test-master-ia32/bld/gcc/xgcc version 14.0.1
20240411 (experimental) [master r14-9913-g467898d513e] (GCC)
=== gfortran tests ===
Running target unix
=== gfortran Summary ===
# of expected passes
A retry build has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2407
Build state: worker not available
Revision: (unknown)
Worker: bb1-1
Build Reason: (unknown)
Blamelist:
A retry build has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2405
Build state: worker not available
Revision: (unknown)
Worker: bb3
Build Reason: (unknown)
Blamelist:
A new failure has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2233
Build state: failed '! grep ...' (failure)
Revision: 4210e02e82289dbf6203418e86fed68153844361
Worker:
A restored build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2234
Build state: build successful
Revision: 895373dea127efb837163564f77c44bbf47538b9
Worker: bb2-1
Build
A new failure has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2465
Build state: failed '! grep ...' (failure)
Revision: 1d28a62a0d75be55fd08c7cf163825d1b7caf967
Worker:
of unsupported tests 4232
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240411
(experimental) [remotes/origin/HEAD r14-9926-g33f83d3cd84] (GCC)
=== gfortran tests ===
Running target unix
XPASS: gfortran.dg/large_real_kind_form_io_2.f90
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2487
Build state: build successful
Revision: d8a697a658e4621abfb7a294cedadb8ac5b285cd
Worker: bb1-2
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114694
--- Comment #2 from Andrew Pinski ---
(In reply to Andrew Pinski from comment #1)
> There might be a dup somewhere ...
PR 93816 is definitely related but it is not a dup since that has no dependent
types but it does have templates being
On Thu, Apr 11, 2024 at 4:02 PM Segher Boessenkool
wrote:
>
> On Wed, Apr 10, 2024 at 08:32:39PM +0200, Uros Bizjak wrote:
> > On Wed, Apr 10, 2024 at 7:56 PM Segher Boessenkool
> > wrote:
> > > This is never okay. You cannot commit a patch without approval, *ever*.
>
> This is the biggest
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2491
Build state: build successful
Revision: 43115c8df9fcbe89fae0af0b9f45146530e6
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2499
Build state: build successful
Revision: b8ce0e28a0114e8a253ab205189f7cb159218a46
Worker: bb1-2
Build
A retry build has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2507
Build state: worker not available
Revision: (unknown)
Worker: bbo1-1
Build Reason: (unknown)
Blamelist:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114699
--- Comment #2 from Richard W.M. Jones ---
This was the stack trace of the crashing thread with gcc-go:
Thread 7 (Thread 0x7ff5c1af3a40 (LWP 2819340)):
#0 0x7ff5c24d67cb in __GI_munmap () at
../sysdeps/unix/syscall-template.S:117
#1
https://gcc.gnu.org/g:f079d69d7b1338522562516537d96e9e1285c95e
commit r14-9927-gf079d69d7b1338522562516537d96e9e1285c95e
Author: David Faust
Date: Thu Apr 11 11:18:55 2024 -0700
btf: emit non-representable bitfield as void
This patch fixes an issue with mangled BTF that could
https://gcc.gnu.org/g:9b8bc02037eeaf4d6365010bb0533385deb4a90d
commit r14-9928-g9b8bc02037eeaf4d6365010bb0533385deb4a90d
Author: David Faust
Date: Thu Apr 11 12:52:36 2024 -0700
btf: fix a possibly misleading asm debug comment
This patch fixes a small error that could occur in
A new failure has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2587
Build state: failed '! grep ...' (failure)
Revision: f02f9672a57f0272996f570a7e8528f832612405
Worker:
of unsupported tests 4232
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240411
(experimental) [remotes/origin/HEAD r14-9927-gf079d69d7b1] (GCC)
=== gfortran tests ===
Running target unix
XPASS: gfortran.dg/large_real_kind_form_io_2.f90
A retry build has been detected on builder gccrust-fedora-x86_64 while building
gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2589
Build state: worker not available
Revision: (unknown)
Worker: bb2-2
Build Reason: (unknown)
Blamelist:
# of expected passes178362
# of unexpected failures128
# of unexpected successes 13
# of expected failures 1595
# of unsupported tests 5017
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240411
(experimental) [remote
Bootstrapped and regtested on x86_64-pc-linux-gnu, OK for trunk?
-- >8 --
While working on some other fixes I noticed that the partition handling
code used the wrong flag to propagate OVL_HIDDEN_P on exported bindings
from partitions. This patch fixes that, and renames the flag to be
clearer.
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2619
Build state: build successful
Revision: 0610584d0d03dc44ce7403dad7028bdc1acceb7e
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2644
Build state: build successful
Revision: c2ea7f6f36c48483a1a776fb51e04214d4526724
Worker: bb1-1
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2646
Build state: build successful
Revision: e99ee91a959cd29e6776c2262512d424ddfeb027
Worker: bb1-2
Build
=== libgo Summary ===
# of expected passes196
/home/tcwg-buildslave/workspace/tcwg_gnu_0/abe/builds/aarch64-unknown-linux-gnu/aarch64-unknown-linux-gnu/gcc-gcc.git~master-stage2/./gcc/gccgo
version 14.0.1 20240411 (experimental) [master revision
gcc-14-9926
git commit g:e0173fbd38df65a35b65230ec2499731a5faaacc
gcc-descr r12-10320-ge0173fbd38df65
power9 BE
Linux 6.7.9-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: Fri Apr 12 01:52:09 UTC 2024
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2685
Build state: build successful
Revision: b620e1d19f19325afe1d49ee8e2b8f6782a19761
Worker: bb1-2
Build
This patch would like to add new sub extension (aka Zfbfmin) to the
-march= option. It introduces a new data type BF16.
1 The Zfbfmin extension depend on 'F', and the FLH, FSH, FMV.X.H, and
FMV.H.X instructions as defined in the Zfh extension.
2 The Zfhmin extension includes the following
LAST_UPDATED: Fri Apr 12 01:40:05 UTC 2024 (revision r14-9929-gd1a21a6f947)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target sde
FAIL: gcc.target/i386/avx-loadu2-m128-1.c scan-assembler \\tvinsertf128\\t
FAIL: gcc.target/i386/avx-loadu2-m128d-1.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114700
--- Comment #8 from lin1.hu at intel dot com ---
(In reply to Andrew Pinski from comment #6)
> Note `c - y - c` to become `-y` reduces the possible of an overflow and is
> well defined for wrapping so this might be still on purpose as there
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2723
Build state: build successful
Revision: b7809f89fb89aa0bef43790c9140cfd4aa8da02f
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2736
Build state: build successful
Revision: 1caf0e8ffed0d4e454470550950cc99eb4bce13a
Worker: bbo2
Build
Regressions on master at commit r14-9913 vs commit r14-9887 on Linux/x86_64
New failures:
FAIL: gcc.dg/guality/pr43051-1.c -O3 -fomit-frame-pointer -funroll-loops
-fpeel-loops -ftracer -finline-functions -DPREVENT_OPTIMIZATION line 34 c ==
[0]
FAIL: gcc.dg/guality/pr43051-1.c -O3
pported tests 3429
=== gcc Summary ===
# of expected passes601997
# of unexpected failures336
# of unexpected successes 60
# of expected failures 4653
# of unsupported tests 10801
/export/gnu/import/git/gcc-test-master-intel64/bld/gcc/xg
Hi,
The former patch adds isfinite optab for __builtin_isfinite.
https://gcc.gnu.org/pipermail/gcc-patches/2024-April/649339.html
Thus the builtin might not be folded at front end. The range op for
isfinite is needed for value range analysis. This patch adds them.
Bootstrapped and tested
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2627
Build state: build successful
Revision: daae0c5dffa45f5300b9af372e13a6ae3ef56366
Worker: bb1-2
Build
A passing build has been detected on builder gccrust-fedora-x86_64 while
building gccrust.
Full details are available at:
https://builder.sourceware.org/buildbot/#/builders/16/builds/2641
Build state: build successful
Revision: f7084d487286e4c7ba2336b7fa567fc59def4c01
Worker: bb1-1
Build
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114700
--- Comment #1 from Andrew Pinski ---
Gcc's trapv is known not always to work correctly.
Try -fsanitize=undefined instead.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114700
Andrew Pinski changed:
What|Removed |Added
See Also||https://gcc.gnu.org/bugzill
git commit g:d1a21a6f9474e519926d20a7c6d664be03aff3ee
gcc-descr r14-9929-gd1a21a6f9474e5
power8
Linux 5.4.0-174-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 Apr 12 02:06:43 UTC 2024
201 - 300 of 487 matches
Mail list logo
