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 rtl-optimization/49477] Should have user/debugger-oriented fine-tuning of optimizations available Date: Tue, 21 Jun 2011 09:50:00 -0000 [thread overview] Message-ID: <bug-49477-4-QWvns6zGvq@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49477-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49477 Richard Guenther <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2011.06.21 09:48:59 CC| |hubicka at gcc dot gnu.org Ever Confirmed|0 |1 --- Comment #1 from Richard Guenther <rguenth at gcc dot gnu.org> 2011-06-21 09:48:59 UTC --- Confirmed. We should 1) disable unneeded optimization at -O0 (we do a lot of folding) 2) look at -O1 (it's basically "untuned" for the last years), make it the intended "reasonable optimization with good compile-time and debugging experience" again. For -O1 my idea was to simply _only_ do early optimizations, thus drop any IPA optimizations from it and not execute pass_all_optimizations. In addition to that from early optimizations disable pass_sra_early, pass_early_ipa_sra and pass_convert_switch. Eventually insert a DSE pass early (not really sure). It'll of course change fundamentally what code we emit for -O1, but at least we have strong CSE/DCE passes and early inlining that is able to remove C++ abstraction. Patch that will arrive there half-way (eventually needs fixing so we still handle some special builtins): Index: gcc/tree-optimize.c =================================================================== --- gcc/tree-optimize.c (revision 175205) +++ gcc/tree-optimize.c (working copy) @@ -53,7 +53,7 @@ along with GCC; see the file COPYING3. static bool gate_all_optimizations (void) { - return (optimize >= 1 + return (optimize > 1 /* Don't bother doing anything if the program has errors. We have to pass down the queue if we already went into SSA */ && (!seen_error () || gimple_in_ssa_p (cfun)));
next prev parent reply other threads:[~2011-06-21 9:50 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-06-20 17:51 [Bug rtl-optimization/49477] New: " amylaar at gcc dot gnu.org 2011-06-21 9:50 ` rguenth at gcc dot gnu.org [this message] 2021-09-12 20:39 ` [Bug rtl-optimization/49477] " pinskia at gcc dot gnu.org 2021-09-13 7:42 ` 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-49477-4-QWvns6zGvq@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: linkBe 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).