public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/112753] [14 Regression] unrecognizable insn building glibc for s390x
Date: Fri, 01 Dec 2023 07:19:20 +0000 [thread overview]
Message-ID: <bug-112753-4-a0yjUWUAdv@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112753-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112753
--- Comment #3 from GCC Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andreas Krebbel <krebbel@gcc.gnu.org>:
https://gcc.gnu.org/g:8a2e428591dc97d573cf5c1789c84c8a3884b364
commit r14-6040-g8a2e428591dc97d573cf5c1789c84c8a3884b364
Author: Juergen Christ <jchrist@linux.ibm.com>
Date: Fri Dec 1 08:01:36 2023 +0100
s390x: Fix s390_md_asm_adjust handling of long doubles [PR112753]
Commit 466b100e5fee808d77598e0f294654deec281150 introduced a bug in
s390_md_asm_adjust if vector extensions are not available. Fix the
control flow of this function to not adjust long double values.
gcc/ChangeLog:
PR target/112753
* config/s390/s390.cc (s390_md_asm_adjust): Return after dealing
with the outputs, if no further processing of long doubles is
required.
gcc/testsuite/ChangeLog:
* gcc.target/s390/pr112753.c: New test.
next prev parent reply other threads:[~2023-12-01 7:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 22:42 [Bug target/112753] New: " jsm28 at gcc dot gnu.org
2023-11-29 6:55 ` [Bug target/112753] " rguenth at gcc dot gnu.org
2023-11-30 20:29 ` jakub at gcc dot gnu.org
2023-11-30 21:03 ` jakub at gcc dot gnu.org
2023-12-01 7:19 ` cvs-commit at gcc dot gnu.org [this message]
2023-12-01 11:55 ` 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-112753-4-a0yjUWUAdv@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).