On 18/12/17 04:09, Sandra Loosemore wrote:
On 12/14/2017 10:50 PM, Sandra Loosemore wrote:
On 12/14/2017 11:48 AM, Kyrill Tkachov wrote:
[snip]
Thanks, done. I haven't created a new Target-specific developers
options table but instead listed the targets the options apply to in
parentheses.
Attached is the latest iteration.
Thank you for the review,
Kyrill
2017-12-14 Kyrylo Tkachov <kyrylo.tkac...@arm.com>
* doc/invoke.texi (GCC Developer options): Add Target-specific
developer options subsection. Populate it with AArch64 and ARM
options.
(Options Summary): List the above.
Hmmm, there are still various problems here, and now I notice that
there's already an entry for -moverride= in the AArch64 Options
section. I need to go through the docs for all targets and make
sure everything is treated uniformly, so I think it would be more
efficient for me to take this over than to continue to iterate with
you to get the patch right. I'll try to get to it this weekend.
OK, I've checked in the attached patch.
I apologize for having given you a bum steer on this previously. :-(
When I dug around in the existing documentation lists, I found a dozen
or more existing target-specific developer options already listed in
the sections for the respective targets (FRV, in particular, has a
whole pile of them documented as "for debugging the compiler"). I
thought it made more sense in terms of the highly target-specific-ness
of what many of these options do to leave them all where they are now,
as well as less work than moving them all to another section. So I
similarly added the docs for the missing ARM and AArch64 developer
options to the existing sections for those respective targets as well.
Thanks Sandra, this does look better now.
Kyrill
-Sandra
