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 testsuite/99685] gcc.target/powerpc/divkc3-1.c and mulkc3-1.c fail for 32 bits
Date: Mon, 17 Oct 2022 20:10:48 +0000	[thread overview]
Message-ID: <bug-99685-4-351RQkNaXb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-99685-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99685

--- Comment #5 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Pat Haugen
<pthaugen@gcc.gnu.org>:

https://gcc.gnu.org/g:7af52b39059b4496b17337d0efc7575f17febb26

commit r10-11043-g7af52b39059b4496b17337d0efc7575f17febb26
Author: Pat Haugen <pthaugen@linux.ibm.com>
Date:   Mon Oct 17 14:53:11 2022 -0500

        Fix register count when not splitting Complex IEEE 128-bit args.

        For ABI_V4, we do not split complex args. This created a problem
because
        even though an arg would be passed in two VSX regs, we were only
advancing the
        function arg counter by one VSX register. Fixed with this patch.

        (backported commit 2ee68beee709e48fce85b8892ff9985acc6a91a8)

    gcc/
            PR target/99685
            * config/rs6000/rs6000-call.c (rs6000_function_arg_advance_1): Bump
            register count when not splitting IEEE 128-bit Complex.

  parent reply	other threads:[~2022-10-17 20:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-20 18:33 [Bug testsuite/99685] New: gcc.target/powerpc/divkc3-1.c and mulkc3-1.c fails " seurer at gcc dot gnu.org
2022-05-17 20:55 ` [Bug testsuite/99685] gcc.target/powerpc/divkc3-1.c and mulkc3-1.c fail " cvs-commit at gcc dot gnu.org
2022-05-17 21:31 ` pthaugen at gcc dot gnu.org
2022-10-03 20:56 ` bergner at gcc dot gnu.org
2022-10-17 19:45 ` cvs-commit at gcc dot gnu.org
2022-10-17 20:10 ` cvs-commit at gcc dot gnu.org [this message]
2022-10-17 20:15 ` cvs-commit at gcc dot gnu.org
2022-10-17 20:47 ` pthaugen 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-99685-4-351RQkNaXb@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).