public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rearnsha at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/107208] [aarch64] _complex integer return types could be improved
Date: Mon, 17 Oct 2022 12:49:14 +0000 [thread overview]
Message-ID: <bug-107208-4-1Bzu9j6nC6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107208-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=107208
--- Comment #4 from Richard Earnshaw <rearnsha at gcc dot gnu.org> ---
(In reply to vfdff from comment #3)
> it seems releted to targetm.calls.function_value called by assign_parms, who
> return different behaviour for MODE_COMPLEX_FLOAT and MODE_COMPLEX_INT. With
> the following changes, then choose a pair of DI for the int case
> ```
> @@ -20333,7 +20333,7 @@ aarch64_vfp_is_call_or_return_candidate
> (machine_mode mode,
> *count = 1;
> new_mode = mode;
> }
> - else if (GET_MODE_CLASS (mode) == MODE_COMPLEX_FLOAT)
> + else if (COMPLEX_MODE_P (mode))
>
> ```
This can't be right. aarch64_vfp_is_call_or_return_candidate is for VFP/SIMD
arguments and complex int is not one of those.
prev parent reply other threads:[~2022-10-17 12:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 3:07 [Bug c++/107208] New: [aarch64] llvm generate better code than gcc base on _Complex type mul zhongyunde at huawei dot com
2022-10-11 3:14 ` [Bug rtl-optimization/107208] " pinskia at gcc dot gnu.org
2022-10-11 4:30 ` [Bug middle-end/107208] [aarch64] _complex integer return types could be improved pinskia at gcc dot gnu.org
2022-10-13 13:32 ` zhongyunde at huawei dot com
2022-10-17 12:49 ` rearnsha at gcc dot gnu.org [this message]
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-107208-4-1Bzu9j6nC6@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).