public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikpe at it dot uu dot se" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/44290] [4.5 Regression] arm linux kernel crahes when built with -fipa-sra
Date: Fri, 28 May 2010 22:03:00 -0000 [thread overview]
Message-ID: <20100528220301.30012.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44290-10179@http.gcc.gnu.org/bugzilla/>
------- Comment #7 from mikpe at it dot uu dot se 2010-05-28 22:02 -------
Bisection identified r148981 as the cause of this regression:
Author: rth
Date: Fri Jun 26 18:23:32 2009
New Revision: 148981
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=148981
Log:
* function.h (struct function): Add cannot_be_copied_reason,
and cannot_be_copied_set.
* tree-inline.c (has_label_address_in_static_1): Rename from
inline_forbidden_p_2; don't set inline_forbidden_reason here.
(cannot_copy_type_1): Rename from inline_forbidden_p_op; likewise
don't set inline_forbidden_reason.
(copy_forbidden): New function, split out of inline_forbidden_p.
(inline_forbidden_p_stmt): Don't check for nonlocal labels here.
(inline_forbidden_p): Use copy_forbidden.
(tree_versionable_function_p): Likewise.
(inlinable_function_p): Merge into tree_inlinable_function_p.
(tree_function_versioning): Remap cfun->nonlocal_goto_save_area.
* ipa-cp.c (ipcp_versionable_function_p): New function.
(ipcp_cloning_candidate_p): Use it.
(ipcp_node_modifiable_p): Likewise.
I'll try to extract a smaller test case tomorrow.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=44290
next prev parent reply other threads:[~2010-05-28 22:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-27 6:26 [Bug tree-optimization/44290] New: " raj dot khem at gmail dot com
2010-05-27 7:07 ` [Bug tree-optimization/44290] " raj dot khem at gmail dot com
2010-05-27 7:13 ` raj dot khem at gmail dot com
2010-05-27 10:41 ` [Bug tree-optimization/44290] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-05-27 17:26 ` raj dot khem at gmail dot com
2010-05-27 17:27 ` raj dot khem at gmail dot com
2010-05-28 11:49 ` mikpe at it dot uu dot se
2010-05-28 22:03 ` mikpe at it dot uu dot se [this message]
2010-05-29 11:36 ` mikpe at it dot uu dot se
2010-05-29 11:43 ` [Bug target/44290] [4.5 Regression] arm linux kernel crahes when built with -fipa-sra, __naked attribute is broken rguenth at gcc dot gnu dot org
2010-05-29 11:47 ` rguenth at gcc dot gnu dot org
2010-05-29 11:50 ` rguenth at gcc dot gnu dot org
2010-05-29 13:30 ` Andrew Pinski
2010-05-29 13:30 ` pinskia at gmail dot com
2010-05-29 14:27 ` mikpe at it dot uu dot se
2010-05-29 14:40 ` mikpe at it dot uu dot se
2010-05-29 14:45 ` [Bug target/44290] [4.5 Regression] " rguenth at gcc dot gnu dot org
2010-05-29 14:46 ` rguenth at gcc dot gnu dot org
2010-05-29 14:47 ` mikpe at it dot uu dot se
2010-05-29 18:00 ` mikpe at it dot uu dot se
2010-05-30 5:58 ` raj dot khem at gmail dot com
2010-05-30 6:55 ` raj dot khem at gmail dot com
2010-05-30 17:04 ` rguenth at gcc dot gnu dot org
2010-07-23 14:48 ` jiez at gcc dot gnu dot org
2010-07-23 14:51 ` jiez at gcc dot gnu dot org
2010-07-23 14:52 ` jiez at gcc dot gnu dot org
2010-07-26 8:05 ` [Bug target/44290] [4.5 only] " ramana at gcc dot gnu dot org
2010-07-26 14:38 ` jiez at gcc dot gnu dot org
2010-07-27 17:34 ` jiez at gcc dot gnu dot org
2010-07-31 9:35 ` rguenth at gcc dot gnu 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=20100528220301.30012.qmail@sourceware.org \
--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: link
Be 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).