public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
* [PATCH, GCC/ARM] Fix comment for cmse_nonsecure_call_clear_caller_saved
@ 2017-05-15 16:28 Thomas Preudhomme
  2017-05-17  9:02 ` Kyrill Tkachov
  0 siblings, 1 reply; 2+ messages in thread
From: Thomas Preudhomme @ 2017-05-15 16:28 UTC (permalink / raw)
  To: Kyrill Tkachov, Ramana Radhakrishnan, Richard Earnshaw, gcc-patches

[-- Attachment #1: Type: text/plain, Size: 768 bytes --]

Hi,

Saving, clearing and restoring of *callee-saved* registers when doing a
cmse_nonsecure_call is done in the __gnu_cmse_nonsecure_call libcall.
Yet, comments for cmse_nonsecure_call_clear_caller_saved claim that
it is this function that does these actions.

This commit fixes the comment to point to the __gnu_cmse_nonsecure_call
libcall instead.

ChangeLog entry is as follows:

*** gcc/ChangeLog ***

2017-05-12  Thomas Preud'homme  <thomas.preudhomme@arm.com>

	* config/arm/arm.c (cmse_nonsecure_call_clear_caller_saved): Refer
	readers to __gnu_cmse_nonsecure_call libcall for saving, clearing and
	restoring of callee-saved registers.

Given that this is just a comment fix, is this ok for trunk and
gcc-7-branch after a one day delay?

Best regards,

Thomas

[-- Attachment #2: fix_cmse_nonsecure_call_clear_calller_saved_comment.patch --]
[-- Type: text/x-patch, Size: 858 bytes --]

diff --git a/gcc/config/arm/arm.c b/gcc/config/arm/arm.c
index 3ae999cb723a234332bd1ca2e80b09df240c67f0..a888e706004d4bd17be2dfc41237bbea691dccb0 100644
--- a/gcc/config/arm/arm.c
+++ b/gcc/config/arm/arm.c
@@ -16909,9 +16909,10 @@ compute_not_to_clear_mask (tree arg_type, rtx arg_rtx, int regno,
   return not_to_clear_mask;
 }
 
-/* Saves callee saved registers, clears callee saved registers and caller saved
-   registers not used to pass arguments before a cmse_nonsecure_call.  And
-   restores the callee saved registers after.  */
+/* Clears caller saved registers not used to pass arguments before a
+   cmse_nonsecure_call.  Saving, clearing and restoring of callee saved
+   registers is done in __gnu_cmse_nonsecure_call libcall.
+   See libgcc/config/arm/cmse_nonsecure_call.S.  */
 
 static void
 cmse_nonsecure_call_clear_caller_saved (void)

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [PATCH, GCC/ARM] Fix comment for cmse_nonsecure_call_clear_caller_saved
  2017-05-15 16:28 [PATCH, GCC/ARM] Fix comment for cmse_nonsecure_call_clear_caller_saved Thomas Preudhomme
@ 2017-05-17  9:02 ` Kyrill Tkachov
  0 siblings, 0 replies; 2+ messages in thread
From: Kyrill Tkachov @ 2017-05-17  9:02 UTC (permalink / raw)
  To: Thomas Preudhomme, Ramana Radhakrishnan, Richard Earnshaw, gcc-patches


On 15/05/17 17:13, Thomas Preudhomme wrote:
> Hi,
>
> Saving, clearing and restoring of *callee-saved* registers when doing a
> cmse_nonsecure_call is done in the __gnu_cmse_nonsecure_call libcall.
> Yet, comments for cmse_nonsecure_call_clear_caller_saved claim that
> it is this function that does these actions.
>
> This commit fixes the comment to point to the __gnu_cmse_nonsecure_call
> libcall instead.
>
> ChangeLog entry is as follows:
>
> *** gcc/ChangeLog ***
>
> 2017-05-12  Thomas Preud'homme  <thomas.preudhomme@arm.com>
>
>     * config/arm/arm.c (cmse_nonsecure_call_clear_caller_saved): Refer
>     readers to __gnu_cmse_nonsecure_call libcall for saving, clearing and
>     restoring of callee-saved registers.
>
> Given that this is just a comment fix, is this ok for trunk and
> gcc-7-branch after a one day delay?
>

Ok.
Thanks,
Kyrill

> Best regards,
>
> Thomas

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2017-05-17  8:51 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-05-15 16:28 [PATCH, GCC/ARM] Fix comment for cmse_nonsecure_call_clear_caller_saved Thomas Preudhomme
2017-05-17  9:02 ` Kyrill Tkachov

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).