public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "xry111 at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/111243] The -Og option inlines functions, making for a poor debugging experience. Date: Fri, 01 Sep 2023 15:43:54 +0000 [thread overview] Message-ID: <bug-111243-4-zXvati2lgo@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111243-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111243 Xi Ruoyao <xry111 at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |xry111 at gcc dot gnu.org --- Comment #4 from Xi Ruoyao <xry111 at gcc dot gnu.org> --- I remember I've asked "why not disable -finline with -Og" via gcc-help and Jonathan told me it would make any "real" C++ programs stupidly slow.
next prev parent reply other threads:[~2023-09-01 15:43 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-30 17:58 [Bug c++/111243] New: " amohr at amohr dot org 2023-08-31 10:46 ` [Bug middle-end/111243] " rguenth at gcc dot gnu.org 2023-08-31 17:31 ` amohr at amohr dot org 2023-09-01 9:09 ` rguenth at gcc dot gnu.org 2023-09-01 15:43 ` xry111 at gcc dot gnu.org [this message] 2023-09-01 16:16 ` redi at gcc dot gnu.org 2023-09-01 16:27 ` redi at gcc dot gnu.org 2023-09-01 16:30 ` redi at gcc dot gnu.org 2023-09-01 16:48 ` amohr at amohr dot org 2023-09-01 16:56 ` xry111 at gcc dot gnu.org 2023-09-01 17:13 ` amohr at amohr dot org 2023-09-01 17:30 ` xry111 at gcc dot gnu.org 2023-09-12 7:10 ` rguenther at suse dot de 2023-09-12 7:29 ` jakub at gcc dot gnu.org 2023-09-12 9:35 ` egallager at gcc dot gnu.org 2023-09-16 23:24 ` amohr at amohr dot 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-111243-4-zXvati2lgo@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).