[COMMITTED] IBM Z: Fix vector intrinsics vec_double and vec_floate

2021-06-17 Thread Marius Hillenbrand via Gcc-patches
Discussed offline with Andreas Krebbel. Fix the mapping of vec_double and vec_floate to builtins. gcc/ChangeLog: PR target/100871 * config/s390/vecintrin.h (vec_doublee): Fix to use __builtin_s390_vflls. (vec_floate): Fix to use __builtin_s390_vflrd.

[PATCH] IBM Z: Avoid bash-specific substitution in configure

2021-05-12 Thread Marius Hillenbrand via Gcc-patches
Tested configure runs on NetBSD x86-64, Linux on x86-64 (with target s390x), and on s390x. Is the patch ok for master, and for gcc-11? 8<--8<--8<- Fix a bootstrap error observed on NetBSD. 2021-05-12 Marius Hillenbrand gcc/ChangeLog: PR bootstrap/100552 *

[PATCH] IBM Z: Fix error checking for builtin vec_permi

2021-05-06 Thread Marius Hillenbrand via Gcc-patches
Hi, this patch fixes the check of immediate operands to the builtin vec_permi and adds a new test for this built-in. Reg-rested and bootstrapped on s390x. Is it OK for master? Is it OK for backporting to gcc-11? Regards, Marius --8<--8<-8<- The builtin vec_permi is

[committed][wwwdocs] gcc-11/changes: Add cross build behavior for --enable-s390-excess-float-precision

2021-01-25 Thread Marius Hillenbrand via Gcc-patches
I pushed a minor update to the existing entry for s390-specific --enable-s390-excess-float-precision after validating. Marius --->8->8-->8->8--- Reflect the changes in commit 33f925094d02 ("IBM Z: Detect libc's float_t behavior on cross compiles"). ---

[COMMITTED] IBM Z: Fix linking to libatomic in target test cases

2021-01-15 Thread Marius Hillenbrand via Gcc-patches
Regtested on s390x-linux-gnu. Approved offline by Andreas Krebbel. Pushed. >8--->8--->8->8--->8--->8- One of the test cases failed to link because of missing paths to libatomic. Reuse procedures in lib/atomic-dg.exp to gather these paths. gcc/testsuite/ChangeLog:

[COMMITTED] MAINTAINERS: Add myself for write after approval.

2020-12-17 Thread Marius Hillenbrand via Gcc-patches
ChangeLog: 2020-12-17 Marius Hillenbrand * MAINTAINERS (Write After Approval): Add myself. --- MAINTAINERS | 1 + 1 file changed, 1 insertion(+) diff --git a/MAINTAINERS b/MAINTAINERS index 32f8a2b7292..48335cc7920 100644 --- a/MAINTAINERS +++ b/MAINTAINERS @@ -428,6 +428,7 @@

[PING] [PATCH] testsuite/libstdc++: Fix required locales of a testcase

2020-12-14 Thread Marius Hillenbrand via Gcc-patches
I'd like to ping the small fixup in https://gcc.gnu.org/pipermail/gcc-patches/2020-November/560100.html Please review and merge, if OK. Marius Forwarded Message Subject: [PATCH] testsuite/libstdc++: Fix required locales of a testcase Date: Tue, 24 Nov 2020 17:26:26 +0100

[PATCH] IBM Z: Detect libc's float_t behavior on cross compiles

2020-12-14 Thread Marius Hillenbrand via Gcc-patches
Hi, Currently, when the option --enable-s390-excess-float-precision is omitted, configure checks the libc's behavior only for native builds yet defaults to the new model for cross compiles. This patch extends the configure-time check to cross-compiles that have target headers available (e.g., in

[PATCH] gcc-11/changes: Document new configure flag --enable-s390-excess-float-precision

2020-11-26 Thread Marius Hillenbrand via Gcc-patches
Hi, To document the new behavior around FLT_EVAL_METHOD and configure flag --enable-s390-excess-float-precision on s390, I propose this update to the Release Notes. Please commit to git-wwwdocs if you agree. Checked against the w3c validator. Thanks, Marius --- htdocs/gcc-11/changes.html | 15

[PATCH 2/2] gcc/testsuite/s390: Add test cases for float_t

2020-11-25 Thread Marius Hillenbrand via Gcc-patches
Add two test cases that check for acceptable combinations of float_t and FLT_EVAL_METHOD on s390x. Tested against an as-is glibc and one modified so that it derives float_t from FLT_EVAL_METHOD. gcc/testsuite/ChangeLog: 2020-11-25 Marius Hillenbrand * gcc.target/s390/float_t-1.c:

[PATCH 1/2] IBM Z: Configure excess precision for float at compile-time

2020-11-25 Thread Marius Hillenbrand via Gcc-patches
Historically, float_t has been defined as double on s390 and gcc would emit double precision insns for evaluating float expressions when in standard-compliant mode. Configure that behavior at compile-time as prep for changes in glibc: When glibc ties float_t to double, keep the old behavior; when

[PATCH 0/2] IBM Z: Prepare cleanup of float express precision

2020-11-25 Thread Marius Hillenbrand via Gcc-patches
Hi, gcc has special behavior for FLT_EVAL_METHOD on s390x that causes performance impact in some scenarios and fails to align with float_t wrt the C standard in others. These two patches prepare gcc for a cleanup to get rid of that special case, to improve standard compliance and avoid the

[PATCH] testsuite/libstdc++: Fix required locales of a testcase

2020-11-24 Thread Marius Hillenbrand via Gcc-patches
The testsuite for libstdc++ aims to skips test cases for which not all required locales are installed. This patch adds missing directives about required locales to one test case to avoid false positive test failures on systems that have a partial set of locales installed. Verified by test suite