From: Sandra Loosemore <sandra@codesourcery.com>
To: "Richard Earnshaw (lists)" <Richard.Earnshaw@arm.com>,
"Andre Vieira (lists)" <Andre.SimoesDiasVieira@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: mickael guene <mickael.guene@st.com>
Subject: Re: [PATCHv2][ARM] -mpure-code option for ARM
Date: Fri, 23 Sep 2016 06:31:00 -0000 [thread overview]
Message-ID: <57E483AD.3020107@codesourcery.com> (raw)
In-Reply-To: <f5498a4d-c3ba-a13c-6a7d-06ec93c29f40@arm.com>
On 09/22/2016 07:52 AM, Richard Earnshaw (lists) wrote:
> On 11/07/16 17:56, Andre Vieira (lists) wrote:
>> +
>> diff --git a/gcc/target.def b/gcc/target.def
>> index a4df363698ce776b51d11c187baed2069ba88a52..a3d46fa48d919a16699c33b2b78236e62a33e025 100644
>> --- a/gcc/target.def
>> +++ b/gcc/target.def
>> @@ -432,6 +432,19 @@ this section is associated.",
>> void, (const char *name, unsigned int flags, tree decl),
>> default_no_named_section)
>>
>> +/* Tell assembler what section attributes to assign this elf section
>> + declaration, using their numerical value. */
>> +DEFHOOK
>> +(elf_flags_numeric,
>> + "If the target needs to represent ELF section attributes using their\n\
>> +numerical value, then this hook should be implemented to return true and\n\
>> +write the numerical value of @var{flags} in @var{num}. This function is\n\
>> +called by @code{default_elf_asm_named_section}, which prints @var{num}\n\
>> +as the value representing the ELF section attributes if this function\n\
>> +returns true.",
>
>
> I think this should read something like.
>
> This hook can be used to encode ELF section flags for which no letter
> code has been defined in the assembler. It is called by
> @code{default_asm_named_section} whenever the section flags need to be
> emitted in the assembler output. If the hook returns true, then the
> numerical value for ELF section flags should be calculated from
> @var{flags} and saved in @var{*num}; the value will be printed out
> instead of the normal sequence of letter codes. If the hook is not
> defined, or if it returns false, then @var{num} will be ignored and the
> traditional letter sequence will be emitted.
Can we please write this in the present tense instead of the future,
assuming it describes current behavior (as modified by the patch)?
s/will be/is/g
-Sandra
next prev parent reply other threads:[~2016-09-23 1:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-30 14:46 [PATCH][ARM] " Andre Vieira (lists)
2016-07-01 19:04 ` Sandra Loosemore
2016-07-07 12:29 ` mickael guene
2016-07-07 12:31 ` mickael guene
2016-07-11 16:57 ` [PATCHv2][ARM] " Andre Vieira (lists)
2016-07-25 10:52 ` [PATCHv2, PING][ARM] " Andre Vieira (lists)
2016-08-11 14:13 ` [PATCHv2, PING 2][ARM] " Andre Vieira (lists)
2016-08-30 8:01 ` [PATCHv2, PING 3][ARM] " Andre Vieira (lists)
2016-09-19 9:25 ` [PATCHv2, PING 4][ARM] " Andre Vieira (lists)
2016-09-22 14:22 ` [PATCHv2][ARM] " Richard Earnshaw (lists)
2016-09-22 15:10 ` [PATCHv3][ARM] " Andre Vieira (lists)
2016-09-22 15:47 ` Richard Earnshaw (lists)
2016-09-22 17:24 ` Andre Vieira (lists)
2016-09-22 19:34 ` Christophe Lyon
2016-09-22 20:05 ` Bill Seurer
2016-09-22 20:30 ` Martin Sebor
2016-09-22 20:20 ` Paolo Carlini
2016-09-23 13:47 ` [PATCH, arm-embedded] " Andre Vieira (lists)
2016-09-23 6:31 ` Sandra Loosemore [this message]
2016-09-23 8:51 ` [PATCHv2][ARM] " Andre Vieira (lists)
2016-09-23 10:41 ` Andre Vieira (lists)
2016-09-23 15:12 ` Sandra Loosemore
2016-10-04 13:24 ` mickael guene
2016-10-04 14:15 ` Andre Vieira (lists)
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=57E483AD.3020107@codesourcery.com \
--to=sandra@codesourcery.com \
--cc=Andre.SimoesDiasVieira@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=mickael.guene@st.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).