From: Richard Sandiford <richard.sandiford@arm.com>
To: Segher Boessenkool <segher@kernel.crashing.org>
Cc: <gcc-patches@gcc.gnu.org>
Subject: Re: [PATCH 0/3] RFC: Let debug stmts influence codegen at -Og
Date: Mon, 24 Jun 2019 14:22:00 -0000 [thread overview]
Message-ID: <mptpnn3gj0q.fsf@arm.com> (raw)
In-Reply-To: <20190624141424.GF7313@gate.crashing.org> (Segher Boessenkool's message of "Mon, 24 Jun 2019 09:14:24 -0500")
Segher Boessenkool <segher@kernel.crashing.org> writes:
> Hi!
>
> What does -O1g do with OPT_LEVELS_1_PLUS_NOT_DEBUG, is it enabled or
> not there? Maybe that name needs to change, with your patches? It is
> currently documented as
>
> /* -O1 (and not -Og) optimizations. */
Yeah, comment should change to be:
/* -O1 and -O1g (but not -Og) optimizations. */
Richard
next prev parent reply other threads:[~2019-06-24 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-23 13:51 Richard Sandiford
2019-06-23 13:52 ` [PATCH 1/3] RFC: Add a mode in which debug stmts participate in codegen Richard Sandiford
2019-06-23 13:53 ` [PATCH 3/3] RFC: Add -O1g Richard Sandiford
2019-06-23 13:53 ` [PATCH 0/3] RFC: Keep debug values live for -Og Richard Sandiford
2019-06-24 12:24 ` [PATCH 0/3] RFC: Let debug stmts influence codegen at -Og Richard Biener
2019-06-24 12:50 ` Richard Sandiford
2019-06-24 14:14 ` Segher Boessenkool
2019-06-24 14:22 ` Richard Sandiford [this message]
2019-06-24 14:28 ` Jakub Jelinek
2019-06-24 14:36 ` Segher Boessenkool
2019-06-24 16:10 ` Richard Sandiford
2019-06-26 8:38 ` [PATCH 0/3] RFC: Let debug stmts influence codegen@-Og Jonathan Wakely
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=mptpnn3gj0q.fsf@arm.com \
--to=richard.sandiford@arm.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=segher@kernel.crashing.org \
/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).