From: "Jérémy Lefaure" <jeremy@lefaure.fr>
To: gcc-patches@gcc.gnu.org
Subject: [PING][PATCH] Fix documentation of -mpoke-function-name ARM option
Date: Fri, 10 Jan 2020 10:23:00 -0000 [thread overview]
Message-ID: <20200110095558.xxoc3juwkihyfxhr@blatinox.fr> (raw)
In-Reply-To: <20191215182025.hrpiacipoc6bxfpk@blatinox.fr>
Hello,
Ping for https://gcc.gnu.org/ml/gcc-patches/2019-12/msg01081.html.
Thank you,
Jérémy
On Sun, Dec 15, 2019 at 07:20:26PM +0100, Jérémy Lefaure wrote:
> Hi!
>
> Since in ARM state the value of PC is the address of the current
> instruction plus 8 bytes, the code inspecting the value of PC stored at
> FP + 0 should look at location PC - 16 : PC - 8 points to the stmfd
> instruction, PC - 16 points two words before, where the top 8 bits are
> set.
>
> gcc/
> 2019-12-14 Jérémy Lefaure <jeremy@lefaure.fr>
>
> * config/arm/arm.c (-mpoke-function-name): Fix documentation in comment.
> * doc/invoke.texi (-mpoke-function-name): Fix documentation.
>
next prev parent reply other threads:[~2020-01-10 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 18:42 [PATCH] " Jérémy Lefaure
2020-01-10 10:23 ` Jérémy Lefaure [this message]
2020-02-20 22:08 ` [PING^2][PATCH] " Jérémy Lefaure
2020-02-24 21:19 ` Sandra Loosemore
2020-03-08 17:19 ` blatinox
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=20200110095558.xxoc3juwkihyfxhr@blatinox.fr \
--to=jeremy@lefaure.fr \
--cc=gcc-patches@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).