public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/100217] [11/12 Regression] ICE when building valgrind testsuite with -march=z14 since r11-7552
Date: Thu, 29 Apr 2021 09:58:49 +0000 [thread overview]
Message-ID: <bug-100217-4-DdGy0NzHVb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-100217-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=100217
--- Comment #13 from Mark Wielaard <mark at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> For valgrind, the quick workaround would be -march=z13 when compiling the
> s390x tests that have register long double variables.
Yes, this works, if fpext and pfpo are build with -march=z13 they compile (and
the tests pass under valgrind).
next prev parent reply other threads:[~2021-04-29 9:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-22 18:24 [Bug target/100217] New: " jakub at gcc dot gnu.org
2021-04-22 18:25 ` [Bug target/100217] " jakub at gcc dot gnu.org
2021-04-22 18:34 ` jakub at gcc dot gnu.org
2021-04-23 8:22 ` jakub at gcc dot gnu.org
2021-04-23 10:27 ` iii at linux dot ibm.com
2021-04-23 10:31 ` jakub at gcc dot gnu.org
2021-04-23 11:00 ` jakub at gcc dot gnu.org
2021-04-23 11:20 ` iii at linux dot ibm.com
2021-04-23 11:27 ` jakub at gcc dot gnu.org
2021-04-23 11:39 ` jakub at gcc dot gnu.org
2021-04-23 11:56 ` iii at linux dot ibm.com
2021-04-26 14:40 ` iii at linux dot ibm.com
2021-04-27 11:40 ` jakub at gcc dot gnu.org
2021-04-28 18:22 ` mark at gcc dot gnu.org
2021-04-28 19:14 ` jakub at gcc dot gnu.org
2021-04-29 9:58 ` mark at gcc dot gnu.org [this message]
2021-05-03 10:50 ` cvs-commit at gcc dot gnu.org
2021-05-06 1:26 ` cvs-commit at gcc dot gnu.org
2021-06-11 13:43 ` jakub at gcc dot gnu.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-100217-4-DdGy0NzHVb@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).