public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "truedfx at gentoo dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/45234] New: ICE in expand_call, at calls.c:2845 when passing aligned function argument from unaligned stack after alloca Date: Sun, 08 Aug 2010 21:04:00 -0000 [thread overview] Message-ID: <bug-45234-9631@http.gcc.gnu.org/bugzilla/> (raw) [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 1187 bytes --] $ cat bug.c extern void f (__float128); void g(void) { __builtin_alloca (2); f (0); } $ gcc -m32 -mpreferred-stack-boundary=2 -c bug.c bug.c: In function g: bug.c:5:5: internal compiler error: in expand_call, at calls.c:2840 Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.gentoo.org/> for instructions. First seen in modified GCC, but with some modifications to the code the ICE also triggers on unpatched GCC on x86 with the above code. Tested with GCC 4.4.4 from Fedora and GCC 4.5.0 from Gentoo. With -mno-accumulate-outgoing-args, GCC accepts the code. -- Summary: ICE in expand_call, at calls.c:2845 when passing aligned function argument from unaligned stack after alloca Product: gcc Version: 4.5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: c AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: truedfx at gentoo dot org GCC build triplet: i686-pc-linux-gnu GCC host triplet: i686-pc-linux-gnu GCC target triplet: i686-pc-linux-gnu http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45234
next reply other threads:[~2010-08-08 21:04 UTC|newest] Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-08-08 21:04 truedfx at gentoo dot org [this message] 2010-08-08 22:01 ` [Bug target/45234] " rguenth at gcc dot gnu dot org 2010-08-08 22:45 ` truedfx at gentoo dot org 2010-08-08 23:10 ` truedfx at gentoo dot org 2010-08-09 15:24 ` ubizjak at gmail dot com 2010-08-09 15:51 ` hjl dot tools at gmail dot com 2010-08-09 16:04 ` [Bug target/45234] [4.4 Regression] " rguenth at gcc dot gnu dot org 2010-08-09 16:16 ` truedfx at gentoo dot org 2010-08-09 16:19 ` hjl dot tools at gmail dot com 2010-08-09 16:29 ` hjl dot tools at gmail dot com 2010-08-09 16:39 ` hjl dot tools at gmail dot com 2010-08-09 16:58 ` truedfx at gentoo dot org 2010-08-09 17:01 ` hjl dot tools at gmail dot com 2010-08-09 17:24 ` hjl dot tools at gmail dot com 2010-08-09 17:44 ` truedfx at gentoo dot org 2010-08-10 5:59 ` truedfx at gentoo dot org 2010-08-10 9:00 ` [Bug target/45234] [4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2010-08-10 13:37 ` [Bug middle-end/45234] " hjl dot tools at gmail dot com 2010-08-30 15:53 ` rguenth at gcc dot gnu dot org 2010-09-06 18:40 ` howarth at nitro dot med dot uc dot edu 2010-09-17 18:01 ` hjl at gcc dot gnu dot org 2010-09-18 20:51 ` sezeroz at gmail dot com 2010-09-20 20:33 ` hjl at gcc dot gnu dot org 2010-09-20 20:39 ` hjl at gcc dot gnu dot org 2010-09-20 20:40 ` hjl dot tools at gmail dot com 2010-09-22 17:24 ` jakub at gcc dot gnu dot org 2010-09-22 21:36 ` hjl dot tools 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-45234-9631@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).