public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "law at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/48470] ICE in expand_expr_addr_expr_1 at expr.c:6835 Date: Mon, 03 Aug 2015 19:35:00 -0000 [thread overview] Message-ID: <bug-48470-4-5lao4KUMJr@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48470-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48470 --- Comment #4 from Jeffrey A. Law <law at gcc dot gnu.org> --- Author: law Date: Mon Aug 3 19:34:31 2015 New Revision: 226528 URL: https://gcc.gnu.org/viewcvs?rev=226528&root=gcc&view=rev Log: PR middle-end/64744 PR middle-end/48470 PR middle-end/43404 * cfgexpand.c (expand_one_var): Add check if stack is going to be used in naked function. * expr.c (expand_expr_addr_expr_1): Remove excess checking whether expression should not reside in MEM. * function.c (use_register_for_decl): Do not use registers for non-register things (volatile, float, BLKMode) in naked functions. PR middle-end/64744 PR middle-end/48470 PR middle-end/43404 * gcc.target/arm/pr43404.c : New testcase. * gcc.target/arm/pr48470.c : New testcase. * gcc.target/arm/pr64744-1.c : New testcase. * gcc.target/arm/pr64744-2.c : New testcase. Added: trunk/gcc/testsuite/gcc.target/arm/pr43404.c trunk/gcc/testsuite/gcc.target/arm/pr48470.c trunk/gcc/testsuite/gcc.target/arm/pr64744-1.c trunk/gcc/testsuite/gcc.target/arm/pr64744-2.c Modified: trunk/gcc/ChangeLog trunk/gcc/cfgexpand.c trunk/gcc/expr.c trunk/gcc/function.c trunk/gcc/testsuite/ChangeLog
next prev parent reply other threads:[~2015-08-03 19:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-04-05 19:41 [Bug c/48470] New: " gcc.ourteddybear at xoxy dot net 2011-04-05 22:30 ` [Bug c/48470] " mikpe at it dot uu.se 2011-04-06 19:48 ` [Bug middle-end/48470] " mikpe at it dot uu.se 2011-07-26 15:57 ` gcc.ourteddybear at xoxy dot net 2015-08-03 19:35 ` law at gcc dot gnu.org [this message] 2015-08-03 19:36 ` law at redhat 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-48470-4-5lao4KUMJr@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).