From: Richard Earnshaw <rearnsha@arm.com>
To: Kyrill Tkachov <kyrylo.tkachov@arm.com>,
GCC Patches <gcc-patches@gcc.gnu.org>
Cc: Ramana Radhakrishnan <Ramana.Radhakrishnan@arm.com>
Subject: Re: [PATCH][doc][ARM] Deprecate -mapcs and -mapcs-frame
Date: Wed, 14 Jan 2015 11:16:00 -0000 [thread overview]
Message-ID: <54B64F76.40907@arm.com> (raw)
In-Reply-To: <54B64721.3050502@arm.com>
On 14/01/15 10:38, Kyrill Tkachov wrote:
> Hi all,
>
> -mapcs-frame (and its' alias -mapcs) are somewhat bitrotten and the ABI
> they represent is deprecated anyway so this is a patch to deprecate the
> option. It's not being removed here, just documented as deprecated.
>
> Kyrill
>
> 2015-01-14 Kyrylo Tkachov <kyrylo.tkachov@arm.com>
>
> * doc/invoke.texi (mapcs): Mention deprecation.
> (mapcs-frame): Likewise.
>
>
> arm-mapcs-deprecated.patch
>
>
> diff --git a/gcc/doc/invoke.texi b/gcc/doc/invoke.texi
> index d2f3c79..7a72120 100644
> --- a/gcc/doc/invoke.texi
> +++ b/gcc/doc/invoke.texi
> @@ -12683,10 +12683,11 @@ Standard for all functions, even if this is not strictly necessary for
> correct execution of the code. Specifying @option{-fomit-frame-pointer}
> with this option causes the stack frames not to be generated for
> leaf functions. The default is @option{-mno-apcs-frame}.
> +This option is deprecated.
>
> @item -mapcs
> @opindex mapcs
> -This is a synonym for @option{-mapcs-frame}.
> +This is a synonym for @option{-mapcs-frame} and is deprecated.
>
> @ignore
> @c not currently implemented
>
OK.
I think this needs a mention in the release notes as well.
R.
next prev parent reply other threads:[~2015-01-14 11:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-14 10:42 Kyrill Tkachov
2015-01-14 11:16 ` Richard Earnshaw [this message]
2015-01-14 11:17 ` Kyrill Tkachov
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=54B64F76.40907@arm.com \
--to=rearnsha@arm.com \
--cc=Ramana.Radhakrishnan@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=kyrylo.tkachov@arm.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).