public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mingw.android at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/61207] New: Win64 gcc 4.9.0: ICE at -Os compiling some C++ code Date: Sat, 17 May 2014 00:44:00 -0000 [thread overview] Message-ID: <bug-61207-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61207 Bug ID: 61207 Summary: Win64 gcc 4.9.0: ICE at -Os compiling some C++ code Product: gcc Version: unknown Status: UNCONFIRMED Severity: major Priority: P3 Component: middle-end Assignee: unassigned at gcc dot gnu.org Reporter: mingw.android at gmail dot com Created attachment 32810 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=32810&action=edit testcase for Win64 gcc 4.9.0 ICE at -Os compiling some C++ code I work on the MSYS2 project and we ran into: g++ -Os -x c++ testcase.i testcase.i: In constructor 'QQuickFlickablePrivate::QQuickFlickablePrivate()': testcase.i:47:10: internal compiler error: in expand_expr_addr_expr_1, at expr.c:7669 {} ^ Please submit a full bug report, with preprocessed source if appropriate. See <http://sourceforge.net/projects/msys2> for instructions. This ICE doesn't happen at -O2 or when specifying the same flags that -Os enables, so I think it is a specific size-optimization that causes this. g++ --version g++.exe (Rev4, Built by MSYS2 project) 4.9.0 .. I also tested with an unpatched version of 4.9.0 with the same results.
next reply other threads:[~2014-05-17 0:44 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-05-17 0:44 mingw.android at gmail dot com [this message] 2014-05-17 0:45 ` [Bug middle-end/61207] " pinskia at gcc dot gnu.org 2014-05-27 11:25 ` ktietz at gcc dot gnu.org 2014-11-20 11:33 ` ktietz at gcc dot gnu.org 2014-11-20 13:45 ` thomas.petazzoni@free-electrons.com 2015-02-08 10:33 ` public at hansmi dot ch 2015-03-06 17:39 ` [Bug middle-end/61207] [4.9 Regression] Win64 gcc 4.9.0: ICE in in expand_expr_addr_expr_1 " doko at gcc dot gnu.org 2015-03-07 5:54 ` kugan at gcc dot gnu.org 2015-03-07 11:09 ` mingw.android at gmail dot com 2015-03-07 16:17 ` ktietz at gcc dot gnu.org 2015-03-08 20:40 ` yroux 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-61207-4@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).