From: Max Filippov <jcmvbkbc@gmail.com>
To: "Takayuki 'January June' Suwa" <jjsuwa_sys3175@yahoo.co.jp>
Cc: GCC Patches <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 1/5] xtensa: Document new -mextra-l32r-costs= Xtensa-specific option
Date: Wed, 15 Jun 2022 17:03:17 -0700 [thread overview]
Message-ID: <CAMo8BfLchM7rqZWQx3kRpoTsybg=yba1tZotmvV05qDNMKcgEQ@mail.gmail.com> (raw)
In-Reply-To: <09db7f8f-5619-ee00-d1f5-1806d01fa068@yahoo.co.jp>
On Mon, Jun 13, 2022 at 8:54 PM Takayuki 'January June' Suwa
<jjsuwa_sys3175@yahoo.co.jp> wrote:
>
>
> gcc/ChangeLog:
> * doc/invoke.texi: Document -mextra-l32r-costs= option.
> ---
> gcc/doc/invoke.texi | 11 ++++++++++-
> 1 file changed, 10 insertions(+), 1 deletion(-)
Committed to master.
--
Thanks.
-- Max
prev parent reply other threads:[~2022-06-16 0:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-14 3:34 Takayuki 'January June' Suwa
2022-06-16 0:03 ` Max Filippov [this message]
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='CAMo8BfLchM7rqZWQx3kRpoTsybg=yba1tZotmvV05qDNMKcgEQ@mail.gmail.com' \
--to=jcmvbkbc@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jjsuwa_sys3175@yahoo.co.jp \
/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).