Hi Frank,
> - just send the emails immediately, without the daemon stuff; if the
> delays are there to try to sequentialize them, consider instead
> getting the hooks to emit Message-Id:/In-Reply-To:/Date: headers to
> let MUA's sort properly at reception
We can certainly add a non-daemon
Hi,
While testing with -Wformat=2, I encountered the following behaviour:
Please see the attached simple C file (tested on gcc 11.2.0/gcc
13.2.1), both give the same warning (clang (17.0.6/gives no warning,
although I am not really sure they have the same effect with the
flags).
It gives the
Hi, Joel -
> [...] Thinking more long term, I think there are talks about using
> a more comprehensive system for source and contribution management,
> similar to products such as GitLab or GitHub. [...]
(Yeah, but I wouldn't count on any of that in the medium term.)
> [...] That's why I tend
Snapshot gcc-12-20240419 is now available on
https://gcc.gnu.org/pub/gcc/snapshots/12-20240419/
and on various mirrors, see https://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 12 git branch
with the following options: git://gcc.gnu.org/git/gcc.git branch
On Thu, 18 Apr 2024 at 07:06, Thomas Koenig via Gcc wrote:
>
> Am 18.04.24 um 01:27 schrieb Mark Wielaard:
> > We also should make sure that all generated files (either in git or in
> > the release/snapshot tar balls) can be reliably and reproducibly
> > regenerated. This also helps the
On 4/18/24 13:41, Arnd Bergmann wrote:
On Thu, Apr 18, 2024, at 17:44, Joseph Myers wrote:
On Wed, 17 Apr 2024, Sandra Loosemore wrote:
Therefore I'd like to mark Nios II as obsolete in GCC 14 now, and remove
support from all toolchain components after the release is made. I'm not sure
2081
# of unexpected failures170
# of unexpected successes 14
# of expected failures 1468
# of unsupported tests 3886
/home/gccbuild/build/nightly/build-gcc-12/gcc/xgcc version 12.3.1 20240419
[remotes/origin/releases/gcc-12 r12-10354-gf04f8734f7] (GCC)
/import/git/gcc-test-master-ia32/bld/gcc/xgcc version 14.0.1
20240419 (experimental) [master-ia32 r14-10039-g9451b6c0a94] (GCC)
=== gfortran tests ===
Running target unix
=== gfortran Summary ===
# of expected passes69699
# of expected failures
On Fri, Apr 19, 2024 at 06:43:13PM +, Qing Zhao wrote:
> Therefore, GCC needs to explicitly allow such extensions directly for C99
> flexible arrays, since flexable array member in unions or alone in structs
> are common code patterns in active use by the Linux kernel (and other
> projects).
https://gcc.gnu.org/g:2afdecccbaf5c5b1c7a235509b37092540906c02
commit r14-10046-g2afdecccbaf5c5b1c7a235509b37092540906c02
Author: Jakub Jelinek
Date: Sat Apr 20 00:12:36 2024 +0200
c-family: Allow arguments with NULLPTR_TYPE as sentinels [PR114780]
While in C++ the ellipsis
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114780
--- Comment #2 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:2afdecccbaf5c5b1c7a235509b37092540906c02
commit r14-10046-g2afdecccbaf5c5b1c7a235509b37092540906c02
Author: Jakub Jelinek
Date:
== gcc Summary ===
# of expected passes178409
# of unexpected failures128
# of unexpected successes 13
# of expected failures 1595
# of unsupported tests 5035
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240419
(experimental) [remotes
Hi All,
This is a more or less obvious patch. The action is in resolve.cc. The
chunk in symbol.cc is a tidy up of a diagnostic marker to distinguish where
the 'no IMPLICIT type' error was coming from and the chunk in trans-decl.cc
follows from discussion with Harald on the PR.
Regtests fine. OK
ss
errors)
=== gcc Summary ===
# of expected passes165764
# of unexpected failures31
# of unexpected successes 3
# of expected failures 1481
# of unsupported tests 2973
/home/gccbuild/build/nightly/build-gcc-13/gcc/xgcc version 13.2.1 20240419
[relea
Regressions on native/master at commit r14-10041 vs commit r14-10039 on
Linux/x86_64
New failures:
New passes:
FAIL: gcc.dg/torture/convert-dfp-2.c -O2 -flto -fuse-linker-plugin
-fno-fat-lto-objects (test for excess errors)
FAIL: gcc.dg/torture/convert-dfp.c -O2 -flto -fuse-linker-plugin
1469
/export/gnu/import/git/gcc-test-master-intel64-native/bld/gcc/xgcc version
14.0.1 20240419 (experimental) [native/master r14-10041-g33bf8e53850] (GCC)
=== g++ tests ===
Running target sde
FAIL: g++.target/i386/mv28.C -std=c++14 (test for errors, line 10)
FAIL: g++.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784
Jakub Jelinek changed:
What|Removed |Added
Ever confirmed|0 |1
CC|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784
Jakub Jelinek changed:
What|Removed |Added
Priority|P3 |P1
--- Comment #3 from Jakub Jelinek
t/powerpc/ppc-fortran/ieee128-math.f90 -O (test for excess
errors)
=== gcc Summary ===
# of expected passes179428
# of unexpected failures97
# of unexpected successes 20
# of expected failures 1612
# of unsupported tests 4251
/home/g
On Fri, 19 Apr 2024, Jakub Jelinek wrote:
> Ok for trunk and later 13.3 if it passes bootstrap/regtest (so far just
> checked on the sentinel related C/C++ tests)?
>
> 2024-04-19 Jakub Jelinek
>
> PR c/114780
> * c-common.cc (check_function_sentinel): Allow as sentinel any
>
GCC maintainers:
The following patch series removes duplicate built-ins. There are patches to
extend an existing overloaded built-in to cover additional input types. The
final patch removes built-ins to set and initialize vectors. The code
generated by these built-ins with the default
rs6000, Remove __builtin_vsx_cmple* builtins
The built-ins __builtin_vsx_cmple_u16qi, __builtin_vsx_cmple_u2di,
__builtin_vsx_cmple_u4si and __builtin_vsx_cmple_u8hi should take
unsigned arguments and return an unsigned result. The current definitions
take signed arguments and return signed
rs6000, Remove __builtin_vsx_xvcvspsxws built-in
The built-in __builtin_vsx_xvcvspsxws is a duplicate of the vec_signed
built-in that is documented in the PVIPR. The __builtin_vsx_xvcvspsxws
built-in is not documented and there are no test cases for it.
This patch removes the redundant
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114746
--- Comment #3 from Joseph S. Myers ---
The actual effect of -fexcess-precision=fast is more like "outside the back
end, pretend excess precision doesn't exist, but the back end might use it
anyway" (complicated a bit by having genuine excess
/nightly/build-gcc-13/gcc/xg++ version 13.2.1 20240419
[releases/gcc-13 r13-8620-g5c3238b0d5] (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=114709
Patrick Palka changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |ppalka at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114782
--- Comment #2 from Andrew Pinski ---
I should note I tested aarch64 (where lea 3 operand instructions are still
cheap) and powerpc (where lea like instructions don't exist) and they produce
what I expect, aarch64 produces an lea like
https://gcc.gnu.org/g:eed7fb1b2fe72150cd6af10dd3b8f7fc4f0a4da1
commit r14-10043-geed7fb1b2fe72150cd6af10dd3b8f7fc4f0a4da1
Author: Jonathan Wakely
Date: Thu Apr 18 12:14:41 2024 +0100
libstdc++: Support link chains in std::chrono::tzdb::locate_zone [PR114770]
Since 2022 the TZif
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114770
--- Comment #1 from GCC Commits ---
The master branch has been updated by Jonathan Wakely :
https://gcc.gnu.org/g:eed7fb1b2fe72150cd6af10dd3b8f7fc4f0a4da1
commit r14-10043-geed7fb1b2fe72150cd6af10dd3b8f7fc4f0a4da1
Author: Jonathan Wakely
y_main() {
run();
}
---
gcc -v output:
GNU C++20
(Compiler-Explorer-Build-gcc-85c187b2127b937e211dfe46b4120d320ff661df-binutils-2.40)
version 14.0.1 20240419 (experimental) (x86_64-linux-gnu)
compiled by GNU C version 11.4.0, GMP version 6.2.1, MPFR version
4.1.0, MPC version 1.2.1, is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784
--- Comment #1 from Daniel Bertalan ---
Forgot to actually post the error message itself:
In constructor 'ErrorOr::ErrorOr(int)',
inlined from 'ErrorOr run()' at :29:10,
inlined from 'int serenity_main()' at :32:8:
:13:39: error:
rs6000, remove __builtin_vsx_vperm_* built-ins
The undocumented built-ins:
__builtin_vsx_vperm_16qi_uns,
__builtin_vsx_vperm_1ti,
__builtin_vsx_vperm_1ti_uns,
__builtin_vsx_vperm_2df,
__builtin_vsx_vperm_2di,
__builtin_vsx_vperm_2di_uns,
__builtin_vsx_vperm_4sf,
of unsupported tests 4249
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240419
(experimental) [remotes/origin/HEAD r14-10043-geed7fb1b2fe] (GCC)
=== gfortran tests ===
Running target unix
XPASS: gfortran.dg/large_real_kind_form_io_2.f90
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114783
--- Comment #3 from Jakub Jelinek ---
Created attachment 57991
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57991=edit
gcc14-pr114783.patch
Full untested patch.
On Mon, 15 Apr 2024, Jakub Jelinek wrote:
> 2024-04-15 Martin Uecker
> Jakub Jelinek
>
> PR lto/114574
> PR c/114361
> gcc/c/
> * c-decl.cc (shadow_tag_warned): For flag_isoc23 and code not
> ENUMERAL_TYPE use SET_TYPE_STRUCTURAL_EQUALITY.
>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784
--- Comment #4 from Jakub Jelinek ---
Guess DECL_UNINLINABLE, maybe DECL_PRESERVE_P, TREE_USED, maybe
DECL_USER_ALIGN/DECL_ALIGN, maybe DECL_WEAK, maybe
DECL_NO_INSTRUMENT_FUNCTION_ENTRY_EXIT, DECL_NO_LIMIT_STACK.
TREE_READONLY, DECL_PURE_P,
rs6000, remove vector set and vector init built-ins.
The vector init built-ins:
__builtin_vec_init_v16qi, __builtin_vec_init_v8hi,
__builtin_vec_init_v4si, __builtin_vec_init_v4sf,
__builtin_vec_init_v2di, __builtin_vec_init_v2df,
__builtin_vec_set_v1ti
perform the same operation as
rs6000, remove __builtin_vsx_xvcmpeqsp built-in
The built-in __builtin_vsx_xvcmpeqsp is a duplicate of the overloaded
vec_cmpeq built-in. The built-in is undocumented. The built-in and
the test cases are removed.
gcc/ChangeLog:
* config/rs6000/rs6000-builtins.def
Bootstrapped/regtested on x86_64-pc-linux-gnu, ok for trunk?
I can defer to 15 if needed, of course.
-- >8 --
When the compiler defaults to -freport-bug, a few dg-ice tests fail
with:
Excess errors:
Preprocessed source stored into /tmp/cc6hldZ0.out file, please attach this to
your bugreport.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114784
--- Comment #5 from Daniel Bertalan ---
I tried Jakub's patch (thank you for the super quick response!), it crashes if
the constructor has non-type template parameters:
template struct SpanImpl {
template SpanImpl();
};
template struct
LAST_UPDATED: Fri Apr 19 16:40:04 UTC 2024 (revision r14-10041-g33bf8e53850)
Native configuration is x86_64-pc-linux-gnu
=== gcc tests ===
Running target unix
XPASS: gcc.dg/Wstringop-overflow-47.c pr97027 (test for warnings, line 72)
XPASS: gcc.dg/Wstringop-overflow-47.c
gcc/testsuite/ChangeLog:
* gcc.dg/flex-array-in-union-1.c: New test.
* gcc.dg/flex-array-in-union-2.c: New test.
---
gcc/testsuite/gcc.dg/flex-array-in-union-1.c | 37 +
gcc/testsuite/gcc.dg/flex-array-in-union-2.c | 42
2 files changed, 79
gcc/testsuite/ChangeLog:
* c-c++-common/builtin-clear-padding-3.c: Adjust testcase.
* g++.dg/ext/flexary12.C: Likewise.
* g++.dg/ext/flexary19.C: Likewise.
* g++.dg/ext/flexary2.C: Likewise.
* g++.dg/ext/flexary3.C: Likewise.
*
gcc/c/ChangeLog:
* c-decl.cc (finish_struct): Change errors to pedwarns for the cases
flexible array members in union or alone in structures.
gcc/cp/ChangeLog:
* class.cc (diagnose_flexarrays): Change error to pdewarn for the case
flexible array members alone in
for allow flexible array members in unions and alone in structures [PR53548]
The request for GCC to accept that the C99 flexible array member can be
in a union or alone in a structure has been made a long time ago around 2012
for supporting several practical cases including glibc.
A GCC PR has
Hi,
The request for GCC to accept that the C99 flexible array member can be
in a union or alone in a struct has been made a long time ago around 2012
for supporting several practical cases including glibc.
A GCC PR has been opened for such request at that time:
failures 5241
# of unsupported tests 23185
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240419
(experimental) [master r14-10041-g33bf8e5385] (GCC)
=== gcc tests ===
Running target unix/-m32
XPASS: gcc.dg/guality/example.c -O0 execution
== gcc Summary ===
# of expected passes178409
# of unexpected failures128
# of unexpected successes 13
# of expected failures 1595
# of unsupported tests 5035
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240419
(experimental) [remotes
rs6000, remove duplicated built-ins of vecmergl and vec_mergeh
The following undocumented built-ins are same as existing documented
overloaded builtins.
const vf __builtin_vsx_xxmrghw (vf, vf);
same as vf __builtin_vec_mergeh (vf, vf); (overloaded vec_mergeh)
const vsi
rs6000, remove __builtin_vsx_xvcmpeqsp_p built-in
The built-in __builtin_vsx_xvcmpeqsp_p is a duplicate of the overloaded
__builtin_altivec_vcmpeqfp_p built-in. The built-in is undocumented and
there are no test cases for it. The patch removes built-in
__builtin_vsx_xvcmpeqsp_p.
gcc/ChangeLog:
rs6000, remove the vec_xxsel built-ins, they are duplicates
The following undocumented built-ins are covered by the existing overloaded
vec_sel built-in definitions.
const vsc __builtin_vsx_xxsel_16qi (vsc, vsc, vsc);
same as vsc __builtin_vec_sel (vsc, vsc, vuc); (overloaded vec_sel)
https://gcc.gnu.org/g:a39983bf58d3097c472252f6989d19b60909dd9a
commit r14-10045-ga39983bf58d3097c472252f6989d19b60909dd9a
Author: Jakub Jelinek
Date: Sat Apr 20 00:05:21 2024 +0200
c: Fix ICE with -g and -std=c23 related to incomplete types [PR114361]
We did not update
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114574
--- Comment #34 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:a39983bf58d3097c472252f6989d19b60909dd9a
commit r14-10045-ga39983bf58d3097c472252f6989d19b60909dd9a
Author: Jakub Jelinek
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114361
--- Comment #8 from GCC Commits ---
The master branch has been updated by Jakub Jelinek :
https://gcc.gnu.org/g:a39983bf58d3097c472252f6989d19b60909dd9a
commit r14-10045-ga39983bf58d3097c472252f6989d19b60909dd9a
Author: Jakub Jelinek
Date:
Hi Paul,
the patch is OK, but I had to manually fix it. I wonder how you managed
to produce:
diff --git a/gcc/testsuite/gfortran.dg/pr93484.f90
b/gcc/testsuite/gfortran.dg/pr93484.f90
new file mode 100644
index 000..4dcad47e8da
--- /dev/null
+++ b/gcc/testsuite/gfortran.dg/pr103471.f90
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114781
anlauf at gcc dot gnu.org changed:
What|Removed |Added
Last reconfirmed||2024-04-19
htly/build-gcc-13/gcc/xgcc version 13.2.1 20240419
[releases/gcc-13 r13-8620-g5c3238b0d5] (GCC)
=== gfortran tests ===
Running target unix
XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O0 execution test
XPASS: gfortran.dg/large_real_kind_form_io_2.f90 -O1 execution
https://gcc.gnu.org/g:e8f0540f23762ca155fe9ed70d6adb864be096b5
commit r14-10042-ge8f0540f23762ca155fe9ed70d6adb864be096b5
Author: Joseph Myers
Date: Fri Apr 19 20:02:56 2024 +
Update gcc sv.po
* sv.po: Update.
Diff:
---
gcc/po/sv.po | 785
> Qing Zhao writes:
> +The size of the union is as if the flexiable array member were omitted
> +except that it may have more trailing padding than the omission would imply.
> +
> +If all the members of a union are flexiable array member, the size of
There's a couple of spots that say
failures 5241
# of unsupported tests 23185
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240419
(experimental) [master r14-10044-gd86472a6f0] (GCC)
=== gcc tests ===
Running target unix/-m32
XPASS: gcc.dg/guality/example.c -O0 execution
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114783
Jakub Jelinek changed:
What|Removed |Added
Status|UNCONFIRMED |NEW
Last reconfirmed|
The patch does not cause failures on AIX. Is it removing explicit
references to /lib and /usr/lib?
It seems more appropriate for GCC 15.
Thanks for alerting me to the patch to test on AIX. AIX is in CFarm.
Thanks David
On Tue, Apr 16, 2024 at 7:49 PM Andrew Pinski (QUIC) <
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114783
Jakub Jelinek changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |jakub at gcc dot gnu.org
of unsupported tests 4249
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240419
(experimental) [remotes/origin/HEAD r14-10041-g33bf8e53850] (GCC)
=== gfortran tests ===
Running target unix
XPASS: gfortran.dg/large_real_kind_form_io_2.f90
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114766
--- Comment #1 from Vladimir Makarov ---
(In reply to Tamar Christina from comment #0)
> The documentation for ^ states:
>
> "This constraint is analogous to ‘?’ but it disparages slightly the
> alternative only if the operand with the ‘^’
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114783
--- Comment #2 from Jakub Jelinek ---
@@ -16831,7 +16882,7 @@ (define_insn "*avx2_eq3"
[(set (match_operand:VI_256 0 "register_operand" "=x")
(eq:VI_256
(match_operand:VI_256 1 "nonimmediate_operand" "%x")
-
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 -s
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114783
Bug ID: 114783
Summary: [14 Regression] Equality compares of vector builtins
spill one operand to the stack
Product: gcc
Version: 14.0
Status: UNCONFIRMED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114782
Andrew Pinski changed:
What|Removed |Added
Resolution|--- |DUPLICATE
Target|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=90088
Andrew Pinski changed:
What|Removed |Added
CC||652023330028 at smail dot
nju.edu.
=== gcc Summary ===
# of expected passes159002
# of unexpected failures49
# of unexpected successes 4
# of expected failures 1396
# of unresolved testcases 11
# of unsupported tests 2880
/home/gccbuild/build/nightly/build-gcc-12/gcc/xgcc ver
ted tests 4125
/export/gnu/import/git/gcc-test-master-ia32/bld/gcc/xgcc version 14.0.1
20240419 (experimental) [master r14-10039-g9451b6c0a94] (GCC)
=== gfortran tests ===
Running target unix
=== gfortran Summary ===
# of expected passes
On Fri, 19 Apr 2024 at 10:08, Jonathan Wakely wrote:
>
> On Fri, 19 Apr 2024 at 07:14, Richard Biener
> wrote:
> >
> > On Thu, Apr 18, 2024 at 6:34 PM Jonathan Wakely wrote:
> > >
> > > This would fix the but, how do people feel about it this close to the
> > > gcc-14 release?
> >
> > Guess
https://gcc.gnu.org/g:d86472a6f041ccf3d1be0cf6bb15d1e0ad8f6dbe
commit r14-10044-gd86472a6f041ccf3d1be0cf6bb15d1e0ad8f6dbe
Author: Jonathan Wakely
Date: Fri Apr 19 17:42:04 2024 +0100
libstdc++: Simplify constraints on <=> for std::reference_wrapper
Instead of constraining these
Tested x86_64-linux. Pushed to trunk.
-- >8 --
Instead of constraining these overloads in terms of synth-three-way we
can just check that the value_type is less-than-comparable, which is
what synth-three-way's constraints check.
The reason that I implemented these with constraints has now been
rs6000, add overloaded vec_sel with int128 arguments
Extend the vec_sel built-in to take three signed/unsigned int128 arguments
and return a signed/unsigned int128 result.
Extending the vec_sel built-in makes the existing buit-ins
__builtin_vsx_xxsel_1ti and __builtin_vsx_xxsel_1ti_uns obsolete.
rs6000, fix error in unsigned vector float to unsigned int built-in definitions
The built-ins __builtin_vsx_vunsigned_v2df and__builtin_vsx_vunsigned_v4sf
are supposed to take a vector of floats and return a vector of unsigned
long long ints. The definitions are using the signed version of the
rs6000, extend the current vec_{un,}signed{e,o} built-ins
The built-ins __builtin_vsx_xvcvspsxds and __builtin_vsx_xvcvspuxds
convert a vector of floats to signed/unsigned long long ints. Extend the
existing vec_{un,}signed{e,o} built-ins to handle the argument
vector of floats to return the
rs6000, remove __builtin_vsx_xvnegdp and __builtin_vsx_xvnegsp built-ins
The undocumented __builtin_vsx_xvnegdp and __builtin_vsx_xvnegsp are
redundant. The overloaded vec_neg built-in provides the same
functionality. The two buit-ins are not documented nor are there any
test cases for them.
rs6000, extend vec_xxpermdi built-in for __int128 args
Add a new overloaded instance for vec_xxpermdi
__int128 vec_xxpermdi (__int128, __int128, const int);
Update the documentation to include a reference to the new built-in
instance.
gcc/ChangeLog:
*
t/powerpc/ppc-fortran/ieee128-math.f90 -O (test for excess
errors)
=== gcc Summary ===
# of expected passes179428
# of unexpected failures97
# of unexpected successes 20
# of expected failures 1612
# of unsupported tests 4251
/home/g
https://gcc.gnu.org/g:9f10005dbc9b660465ec4a9640bcbdcc1e5171c3
commit r14-10050-g9f10005dbc9b660465ec4a9640bcbdcc1e5171c3
Author: Pan Li
Date: Sat Apr 20 09:02:39 2024 +0800
RISC-V: Add xfail test case for wv insn register overlap
We reverted below patch for wv insn overlap, add
ted tests 4125
/export/gnu/import/git/gcc-test-master-ia32/bld/gcc/xgcc version 14.0.1
20240419 (experimental) [master r14-10044-gd86472a6f04] (GCC)
=== gfortran tests ===
Running target unix
=== gfortran Summary ===
# of expected passes
git commit g:9f10005dbc9b660465ec4a9640bcbdcc1e5171c3
gcc-descr r14-10050-g9f10005dbc9b66
power9
Linux 5.15.0-97-generic ppc64le
GNU Make 4.3
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat Apr 20 02:30:12 UTC 2024
Hi!
The r14-4456 change (part of APX EGPR support) seems to have mistakenly
changed in the
@@ -16831,7 +16831,7 @@ (define_insn "*avx2_eq3"
[(set (match_operand:VI_256 0 "register_operand" "=x")
(eq:VI_256
(match_operand:VI_256 1 "nonimmediate_operand" "%x")
-
outputs-23 exe savetmp named2-2: outputs.ld1_args
FAIL: outputs-24 exe savetmp named2-3: outputs.ld1_args
FAIL: outputs-25 exe savetmp named2-4: outputs.ld1_args
FAIL: outputs-294 lto sing unnamed-3: a.ld1_args
FAIL: outputs-294 lto sing unnamed-3: a.ld_args
=== gcc Summary ===
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=114785
--- Comment #2 from Andrew Pinski ---
I think the code code in maybe_push_res_to_seq for COMPARISON_CLASS_P can be
removed too ...
== gcc Summary ===
# of expected passes178420
# of unexpected failures128
# of unexpected successes 13
# of expected failures 1595
# of unsupported tests 5035
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xgcc version 14.0.1 20240419
(experimental) [remotes
https://gcc.gnu.org/g:f5447eae72f11d9bfbb403183fd282918c0445c6
commit r14-10051-gf5447eae72f11d9bfbb403183fd282918c0445c6
Author: Pan Li
Date: Sat Apr 20 09:42:57 2024 +0800
Revert "RISC-V: Support highest overlap for wv instructions"
This reverts commit
git commit g:c59869f23ebeb1fef38de24d05dbb035031c3097
gcc-descr r13-8621-gc59869f23ebeb1
power9
Linux 5.15.0-97-generic ppc64le
GNU Make 4.3
DejaGnu:
DejaGnu version 1.6.2
Expect version 5.45.4
Tcl version 8.6
64-bit
LAST_UPDATED: Sat Apr 20 04:01:30 UTC 2024
git commit g:9f10005dbc9b660465ec4a9640bcbdcc1e5171c3
gcc-descr r14-10050-g9f10005dbc9b66
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: Sat Apr 20 03:18:00 UTC 2024
1469
/export/gnu/import/git/gcc-test-master-intel64-native/bld/gcc/xgcc version
14.0.1 20240419 (experimental) [native/master r14-10044-gd86472a6f04] (GCC)
=== g++ tests ===
Running target sde
FAIL: g++.target/i386/mv28.C -std=c++14 (test for errors, line 10)
FAIL: g++.
t/powerpc/ppc-fortran/ieee128-math.f90 -O (test for excess
errors)
=== gcc Summary ===
# of expected passes179439
# of unexpected failures97
# of unexpected successes 20
# of expected failures 1612
# of unsupported tests 4251
/home/g
Committed, thanks Juzhe.
Pan
From: juzhe.zh...@rivai.ai
Sent: Saturday, April 20, 2024 9:20 AM
To: Li, Pan2 ; gcc-patches
Cc: kito.cheng ; Robin Dapp ; Li,
Pan2
Subject: Re: [PATCH v1] RISC-V: Add xfail test case for wv insn register overlap
LGTM.
\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-assembler vpopcth\\t%v24,%v24
=== gcc Summary for unix/-m64 ===
# of expected passes180862
# of unexpected failures173
# of unex
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112893
--- Comment #8 from Gaius Mulley ---
Created attachment 57992
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57992=edit
Proposed fix v3
This patch creates a proctype for every procedure and then uses this associated
proctype during type
failures 5241
# of unsupported tests 23185
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240419
(experimental) [master r14-10046-g2afdecccba] (GCC)
=== gcc tests ===
Running target unix/-m32
XPASS: gcc.dg/guality/example.c -O0 execution
https://gcc.gnu.org/g:0cbeafe26513954b0aea3293d2f82d4863f10f1d
commit r14-10049-g0cbeafe26513954b0aea3293d2f82d4863f10f1d
Author: Pan Li
Date: Sat Apr 20 08:29:38 2024 +0800
Revert "RISC-V: Support one more overlap for wv instructions"
This reverts commit
failures 5241
# of unsupported tests 23185
/home/gccbuild/build/nightly/build-gcc-trunk/gcc/xg++ version 14.0.1 20240419
(experimental) [master r14-10047-gc23db3ebb6] (GCC)
=== gcc tests ===
Running target unix/-m32
XPASS: gcc.dg/guality/example.c -O0 execution
git commit g:9e44e2f767c6fa1a658964feb6306e9672d26d01
gcc-descr r12-10355-g9e44e2f767c6fa
power9 IEEE128
Linux 6.9.0-0.rc3.30.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 Apr 20
1 - 100 of 296 matches
Mail list logo