From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: hongjie wu <hongjiewu1225@gmail.com>
Cc: gcc@gcc.gnu.org
Subject: Re: The method of determining the specific assignment of gcc optimization options
Date: Fri, 9 Dec 2022 14:40:42 +0000 [thread overview]
Message-ID: <CAH6eHdQ+hLhJ2wE4EbgoVfZhdFS2MWfS4DE=_DEyg1F0OeCEfw@mail.gmail.com> (raw)
In-Reply-To: <CAEKG5iCx1tM0THyL6XyW9k1JxqWVfJ9RRuP4Bjf_JXG6ZRayrw@mail.gmail.com>
This question belongs on the gcc-help mailing list, not here.
On Fri, 9 Dec 2022 at 12:01, hongjie wu via Gcc <gcc@gcc.gnu.org> wrote:
>
> Dear Sir or Madam,
> I want to know how to obtain optimal level of the value of the
What do you mean by optimal?
They have pros and cons.
> specific compiler options, for example - fexcess - precision = [fast |
> standard] [default], including the default represent?Or how to determine?
gcc -Q --help=optim
> I am looking forward to your favorable replay.
next prev parent reply other threads:[~2022-12-09 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-09 12:00 hongjie wu
2022-12-09 14:40 ` Jonathan Wakely [this message]
2022-12-10 2:01 ` hongjie wu
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='CAH6eHdQ+hLhJ2wE4EbgoVfZhdFS2MWfS4DE=_DEyg1F0OeCEfw@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=hongjiewu1225@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).