From: Wilco Dijkstra <Wilco.Dijkstra@arm.com>
To: Richard Biener <richard.guenther@gmail.com>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>,
Kyrylo Tkachov <Kyrylo.Tkachov@arm.com>,
Richard Earnshaw <Richard.Earnshaw@arm.com>, nd <nd@arm.com>
Subject: Re: [PATCH][ARM] Enable code hoisting with -Os (PR80155)
Date: Thu, 12 Sep 2019 11:29:00 -0000 [thread overview]
Message-ID: <HE1PR0801MB2121F05D4DDBE11204E52A4083B00@HE1PR0801MB2121.eurprd08.prod.outlook.com> (raw)
In-Reply-To: <CAFiYyc1oGrENhesPgibzEFz11jb=okkfz-2ZAOHkYrey-TFy-g@mail.gmail.com>
Hi Richard,
> Do we document target specific deviations from "default" behavior somewhere?
Not as far as I know. The other option changes in arm-common.c are not mentioned
anywhere, neither is any of arm_option_override_internal.
If we want to keep documentation useful, we shouldn't clutter the generic options
with target-specific deviations from the default settings. What might be feasible is
adding a section for each target which describes changes from the default settings.
Wilco
next prev parent reply other threads:[~2019-09-12 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-11 15:50 Wilco Dijkstra
2019-09-12 9:54 ` Richard Biener
2019-09-12 11:29 ` Wilco Dijkstra [this message]
2019-09-12 11:55 ` Richard Biener
2019-09-14 21:49 ` Prathamesh Kulkarni
2019-09-16 12:58 ` Wilco Dijkstra
2019-09-16 13:31 ` Richard Biener
2019-09-17 17:18 ` Wilco Dijkstra
2019-09-18 8:47 ` Richard Biener
2019-09-18 16:47 ` Prathamesh Kulkarni
2019-09-19 1:28 ` Prathamesh Kulkarni
2019-09-19 10:47 ` Richard Biener
2019-09-19 10:37 ` Richard Biener
2019-10-10 10:40 ` Joey Ye
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=HE1PR0801MB2121F05D4DDBE11204E52A4083B00@HE1PR0801MB2121.eurprd08.prod.outlook.com \
--to=wilco.dijkstra@arm.com \
--cc=Kyrylo.Tkachov@arm.com \
--cc=Richard.Earnshaw@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=nd@arm.com \
--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).