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/106355] Linux s390x -O2 argument passing miscompile Date: Tue, 25 Oct 2022 08:39:14 +0000 [thread overview] Message-ID: <bug-106355-4-97olunEHwi@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-106355-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106355 --- Comment #8 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The releases/gcc-10 branch has been updated by Stefan Schulze Frielinghaus <stefansf@gcc.gnu.org>: https://gcc.gnu.org/g:97509e98d9199ff43916250fc0a20f3d1838d067 commit r10-11059-g97509e98d9199ff43916250fc0a20f3d1838d067 Author: Stefan Schulze Frielinghaus <stefansf@linux.ibm.com> Date: Tue Oct 25 10:38:23 2022 +0200 IBM zSystems: Fix function_ok_for_sibcall [PR106355] For a parameter with BLKmode we cannot use REG_NREGS in order to determine the number of consecutive registers. Streamlined this with the implementation of s390_function_arg. Fix some indentation whitespace, too. gcc/ChangeLog: PR target/106355 * config/s390/s390.c (s390_call_saved_register_used): For a parameter with BLKmode fix determining number of consecutive registers. gcc/testsuite/ChangeLog: * gcc.target/s390/pr106355.h: Common code for new tests. * gcc.target/s390/pr106355-1.c: New test. * gcc.target/s390/pr106355-2.c: New test. * gcc.target/s390/pr106355-3.c: New test. (cherry picked from commit cb994acc08b67f26a54e7c5dc1f4995a2ce24d98)
next prev parent reply other threads:[~2022-10-25 8:39 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-07-19 14:28 [Bug other/106355] New: " sbergman at redhat dot com 2022-07-20 8:06 ` [Bug target/106355] " rguenth at gcc dot gnu.org 2022-07-20 8:14 ` sbergman at redhat dot com 2022-08-15 13:00 ` dan at danny dot cz 2022-08-15 13:20 ` stefansf at linux dot ibm.com 2022-10-19 12:29 ` cvs-commit at gcc dot gnu.org 2022-10-25 8:35 ` cvs-commit at gcc dot gnu.org 2022-10-25 8:37 ` cvs-commit at gcc dot gnu.org 2022-10-25 8:39 ` cvs-commit at gcc dot gnu.org [this message] 2024-02-29 20:19 ` mpolacek 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-106355-4-97olunEHwi@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: linkBe 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).