public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/48031] [4.4/4.5 Regression] gcc.c-torture/compile/pr42956.c ICEs gcc on m68k-linux, ivopts related?
Date: Thu, 10 Mar 2011 09:34:00 -0000 [thread overview]
Message-ID: <bug-48031-4-Lx4iSLBuKe@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48031-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48031
--- Comment #6 from rguenther at suse dot de <rguenther at suse dot de> 2011-03-10 09:33:49 UTC ---
On Thu, 10 Mar 2011, mikpe at it dot uu.se wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48031
>
> --- Comment #5 from Mikael Pettersson <mikpe at it dot uu.se> 2011-03-10 09:22:04 UTC ---
> If I revert this part of r139061 then things work again:
>
> * gimplify.c (gimplify_conversion): Use maybe_fold_offset_to_address.
>
> --- gcc/gimplify.c (revision 139060)
> +++ gcc/gimplify.c (revision 139061)
> @@ -1842,17 +1842,13 @@ gimplify_conversion (tree *expr_p)
> /* Attempt to avoid NOP_EXPR by producing reference to a subtype.
> For example this fold (subclass *)&A into &A->subclass avoiding
> a need for statement. */
> - if (TREE_CODE (*expr_p) == NOP_EXPR
> + if (CONVERT_EXPR_P (*expr_p)
> && POINTER_TYPE_P (TREE_TYPE (*expr_p))
> && POINTER_TYPE_P (TREE_TYPE (TREE_OPERAND (*expr_p, 0)))
> - && (tem = maybe_fold_offset_to_reference
> + && (tem = maybe_fold_offset_to_address
> (TREE_OPERAND (*expr_p, 0),
> - integer_zero_node, TREE_TYPE (TREE_TYPE (*expr_p)))))
> - {
> - tree ptr_type = build_pointer_type (TREE_TYPE (tem));
> - if (useless_type_conversion_p (TREE_TYPE (*expr_p), ptr_type))
> - *expr_p = build_fold_addr_expr_with_type (tem, ptr_type);
> - }
> + integer_zero_node, TREE_TYPE (*expr_p))) != NULL_TREE)
> + *expr_p = tem;
>
> /* If we still have a conversion at the toplevel,
> then canonicalize some constructs. */
>
> The first condition change is Ok, it's the change to call m_f_o_t_address
> instead of m_f_o_t_reference and the then-clause change that matter.
>
> Reverting this from trunk @ r139061 + r151559 backport, or trunk @ r151559,
> eliminates the ICE.
I think this is all just the right circumstances for triggering the bug.
next prev parent reply other threads:[~2011-03-10 9:34 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-08 10:01 [Bug target/48031] New: [4,4, 4.5 regression] " mikpe at it dot uu.se
2011-03-08 11:02 ` [Bug tree-optimization/48031] [4.4/4.5 Regression] " rguenth at gcc dot gnu.org
2011-03-08 14:23 ` mikpe at it dot uu.se
2011-03-08 21:40 ` mikpe at it dot uu.se
2011-03-09 9:22 ` rguenther at suse dot de
2011-03-09 23:37 ` mikpe at it dot uu.se
2011-03-10 9:22 ` mikpe at it dot uu.se
2011-03-10 9:34 ` rguenther at suse dot de [this message]
2011-03-10 11:03 ` rguenth at gcc dot gnu.org
2011-03-10 12:35 ` ebotcazou at gcc dot gnu.org
2011-03-10 12:36 ` rguenther at suse dot de
2011-03-10 12:46 ` ebotcazou at gcc dot gnu.org
2011-03-10 12:58 ` rguenther at suse dot de
2011-03-10 13:04 ` ebotcazou at gcc dot gnu.org
2011-03-10 13:07 ` rguenther at suse dot de
2011-03-10 13:10 ` rguenth at gcc dot gnu.org
2011-03-10 14:03 ` mikpe at it dot uu.se
2011-03-15 8:53 ` mikpe at it dot uu.se
2011-03-15 10:06 ` rguenth at gcc dot gnu.org
2011-03-28 10:22 ` rguenth at gcc dot gnu.org
2011-04-10 10:38 ` rguenth at gcc dot gnu.org
2011-04-16 11:18 ` jakub at gcc dot gnu.org
2011-04-18 14:15 ` [Bug tree-optimization/48031] [4.4 " rguenth at gcc dot gnu.org
2011-04-18 14:42 ` [Bug tree-optimization/48031] [4.4/4.5 " rguenth at gcc dot gnu.org
2011-04-18 14:55 ` [Bug tree-optimization/48031] [4.4 " rguenth at gcc dot gnu.org
2012-03-13 16:57 ` jakub 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-48031-4-Lx4iSLBuKe@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: 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).