public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/53316] Introduce -Odebug
Date: Fri, 11 May 2012 08:41:00 -0000 [thread overview]
Message-ID: <bug-53316-4-9P6ywlm8VR@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-53316-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53316
Richard Guenther <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed| |2012-05-11
AssignedTo|unassigned at gcc dot |rguenth at gcc dot gnu.org
|gnu.org |
Summary|Change -O1 to be easily |Introduce -Odebug
|debugged and on by default |
Ever Confirmed|0 |1
--- Comment #5 from Richard Guenther <rguenth at gcc dot gnu.org> 2012-05-11 08:38:41 UTC ---
(In reply to comment #4)
> > As it stands, does anyone even use -O1? It seems like it would be a major
> > improvement to make it useful.
>
> Of course people do use -O1 and making such an incompatible change to it is out
> of question I think. That's largely orthogonal to introducing -Odebug (and
> making it the default) in my opinion.
Of course people should realize that -O1 is by no means "maintained" as in
tuned in any way to do something reasonable. At the moment it wastes much
time for no good reason, just selectively turning off some optimizations.
Re-tuning -O1 definitely makes sense - maybe not to the point we'd want to
go with -Odebug.
I'm taking this bug as a request to add -Odebug, something I was working on,
so - mine.
next prev parent reply other threads:[~2012-05-11 8:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-10 23:13 [Bug other/53316] New: Change -O1 to be easily debugged and on by default DeusExSophismata at gmail dot com
2012-05-10 23:18 ` [Bug other/53316] " pinskia at gcc dot gnu.org
2012-05-10 23:32 ` DeusExSophismata at gmail dot com
2012-05-11 5:57 ` jakub at gcc dot gnu.org
2012-05-11 6:27 ` ebotcazou at gcc dot gnu.org
2012-05-11 8:41 ` rguenth at gcc dot gnu.org [this message]
2012-05-11 8:55 ` [Bug other/53316] Introduce -Odebug jakub at gcc dot gnu.org
2012-05-11 9:01 ` rguenth at gcc dot gnu.org
2012-05-11 9:01 ` rguenth at gcc dot gnu.org
2012-05-11 15:52 ` david at doublewise dot net
2012-05-16 16:15 ` david at doublewise dot net
2012-09-19 9:30 ` rguenth at gcc dot gnu.org
2012-09-19 9:32 ` rguenth at gcc dot gnu.org
2012-09-19 9:33 ` [Bug other/53316] Introduce -Og rguenth at gcc dot gnu.org
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=bug-53316-4-9P6ywlm8VR@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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).