public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "belegdol at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/95949] mame build succeeds with -O3 but fails with -O2 and all -O3 flags added manually Date: Thu, 30 Jul 2020 14:21:37 +0000 [thread overview] Message-ID: <bug-95949-4-51T4MpbiwN@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-95949-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95949 W E Brown <webrown.cpp at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |webrown.cpp at gmail dot com Julian Sikorski <belegdol at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Version|10.1.0 |10.2.0 --- Comment #10 from Julian Sikorski <belegdol at gmail dot com> --- 10.2.0 is still affected.
next prev parent reply other threads:[~2020-07-30 14:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-28 15:59 [Bug c++/95949] New: " belegdol at gmail dot com 2020-06-28 16:00 ` [Bug c++/95949] " belegdol at gmail dot com 2020-06-28 16:02 ` belegdol at gmail dot com 2020-06-29 10:41 ` rguenth at gcc dot gnu.org 2020-06-29 12:42 ` redi at gcc dot gnu.org 2020-06-29 16:11 ` belegdol at gmail dot com 2020-06-29 17:20 ` redi at gcc dot gnu.org 2020-06-29 17:23 ` redi at gcc dot gnu.org 2020-06-29 17:38 ` belegdol at gmail dot com 2020-06-29 20:17 ` redi at gcc dot gnu.org 2020-07-30 14:21 ` belegdol at gmail dot com [this message] 2021-12-17 19:39 ` belegdol at gmail dot com
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-95949-4-51T4MpbiwN@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).