From: HAO CHEN GUI <guihaoc@linux.ibm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH, expand] Call misaligned memory reference in expand_builtin_return [PR112417]
Date: Fri, 10 Nov 2023 15:52:27 +0800 [thread overview]
Message-ID: <b537dc9f-9242-4f62-84cb-4f0f42eec7ee@linux.ibm.com> (raw)
In-Reply-To: <CAFiYyc3Ft+vOKzAtUviogqvteiAo6J_joLMYrA383xXwHnBj+w@mail.gmail.com>
Hi Richard,
Thanks so much for your comments.
在 2023/11/9 19:41, Richard Biener 写道:
> I'm not sure if the testcase is valid though?
>
> @defbuiltin{{void} __builtin_return (void *@var{result})}
> This built-in function returns the value described by @var{result} from
> the containing function. You should specify, for @var{result}, a value
> returned by @code{__builtin_apply}.
> @enddefbuiltin
>
> I don't see __builtin_apply being used here?
The prototype of the test case is from "__objc_block_forward" in
libobjc/sendmsg.c.
void *args, *res;
args = __builtin_apply_args ();
res = __objc_forward (rcv, op, args);
if (res)
__builtin_return (res);
else
...
The __builtin_apply_args puts the return values on stack by the alignment.
But the forward function can do anything and return a void* pointer.
IMHO the alignment might be broken. So I just simplified it to use a
void* pointer as the input argument of "__builtin_return" and skip
"__builtin_apply_args".
Thanks
Gui Haochen
next prev parent reply other threads:[~2023-11-10 7:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-09 5:41 HAO CHEN GUI
2023-11-09 11:41 ` Richard Biener
2023-11-10 7:52 ` HAO CHEN GUI [this message]
2023-11-10 9:06 ` Richard Biener
2023-11-10 10:09 ` HAO CHEN GUI
2023-11-10 13:39 ` Richard Biener
[not found] ` <e8bfd189-5c8b-4a1b-bc84-d3fe0cb1a032@linux.ibm.com>
2023-11-13 8:09 ` Fwd: " HAO CHEN GUI
2023-11-13 9:38 ` Richard Biener
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=b537dc9f-9242-4f62-84cb-4f0f42eec7ee@linux.ibm.com \
--to=guihaoc@linux.ibm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=richard.guenther@gmail.com \
/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).