public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Daniel Berlin" <dberlin@dberlin.org>
To: "Hans-Peter Nilsson" <hans-peter.nilsson@axis.com>
Cc: gcc-patches@gcc.gnu.org
Subject: Re: ICE caused by "[PATCH]: Rewrite tree level PRE"
Date: Wed, 09 Jul 2008 17:35:00 -0000	[thread overview]
Message-ID: <4aca3dc20807091009n52015b9cr1c53b7ab929211bd@mail.gmail.com> (raw)
In-Reply-To: <200807090126.m691Qlw9021221@ignucius.se.axis.com>

[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]

The attached patch fixes the fortran failure.
Bootstrapped and regtested on i686-linux-gnu

Committed to mainline

2008-07-09  Daniel Berlin  <dberlin@dberlin.org>

        * tree-ssa-pre.c (phi_translate_1): Update placement of
        add_to_value calls.


> Running /tmp/hpautotest-gcc1/gcc/gcc/testsuite/gfortran.fortran-torture/compile/compile.exp ...
> FAIL: gfortran.fortran-torture/compile/pr32663.f,  -O2   (internal compiler error)
> FAIL: gfortran.fortran-torture/compile/pr32663.f,  -O2 -fomit-frame-pointer -finline-functions   (internal compiler error)
> FAIL: gfortran.fortran-torture/compile/pr32663.f,  -O2 -fomit-frame-pointer -finline-functions -funroll-loops   (internal compiler error)
> FAIL: gfortran.fortran-torture/compile/pr32663.f,  -O3 -g   (internal compiler error)
>
> in gfortran.log:
> x/gcc/testsuite/gfortran.fortran-torture/compile/pr32663.f: In function 'dimoid':
> x/gcc/testsuite/gfortran.fortran-torture/compile/pr32663.f:1: internal compiler error: Segmentation fault
>
> brgds, H-P
>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: fixfortran.diff --]
[-- Type: text/x-diff; name=fixfortran.diff, Size: 772 bytes --]

Index: tree-ssa-pre.c
===================================================================
--- tree-ssa-pre.c	(revision 137631)
+++ tree-ssa-pre.c	(working copy)
@@ -1399,8 +1399,8 @@ phi_translate_1 (pre_expr expr, bitmap_s
 		if (constant != expr)
 		  return constant;
 		get_or_alloc_expression_id (expr);
-		add_to_value (new_val_id, expr);
 	      }
+	    add_to_value (new_val_id, expr);
 	  }
 	phi_trans_add (oldexpr, expr, pred);
 	return expr;
@@ -1532,8 +1532,8 @@ phi_translate_1 (pre_expr expr, bitmap_s
 						     result, new_val_id);
 		PRE_EXPR_REFERENCE (expr) = newref;
 		get_or_alloc_expression_id (expr);
-		add_to_value (new_val_id, expr);
 	      }
+	    add_to_value (new_val_id, expr);
 	  }
 	phi_trans_add (oldexpr, expr, pred);
 	return expr;

  parent reply	other threads:[~2008-07-09 17:09 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-06  4:48 [PATCH]: Rewrite tree level PRE Daniel Berlin
2008-07-06  8:58 ` Ralf Wildenhues
2008-07-06 19:24   ` Daniel Berlin
2008-07-06 15:23 ` Richard Guenther
2008-07-06 19:19   ` Daniel Berlin
2008-07-06 22:12     ` Daniel Berlin
2008-07-07 16:49       ` Daniel Berlin
2008-07-08 16:42         ` Daniel Berlin
2008-07-09  2:10           ` ICE caused by "[PATCH]: Rewrite tree level PRE" Hans-Peter Nilsson
2008-07-09  8:21             ` Daniel Berlin
2008-07-09  9:07               ` Richard Guenther
2008-07-09 17:35             ` Daniel Berlin [this message]
2008-07-11 13:12   ` [PATCH]: Rewrite tree level PRE Eric Botcazou
2008-07-11 14:01     ` Richard Guenther
2008-07-11 18:22     ` Daniel Berlin
2008-07-11 18:40       ` Eric Botcazou

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=4aca3dc20807091009n52015b9cr1c53b7ab929211bd@mail.gmail.com \
    --to=dberlin@dberlin.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hans-peter.nilsson@axis.com \
    /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).