public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Laurent GUERBY <laurent@guerby.net>
To: gcc-patches@gcc.gnu.org
Cc: gcc@gcc.gnu.org, Richard Kenner <kenner@vlsi1.ultra.nyu.edu>
Subject: PR22336 (was: Problem with tree-ssa-loop-ivopts.c:get_computation-cost)
Date: Tue, 12 Jul 2005 10:04:00 -0000	[thread overview]
Message-ID: <1121162567.11810.150.camel@m.site> (raw)
In-Reply-To: <1120552288.7662.62.camel@m.site>

If no one is suggesting an alternative, tested on x86 and x86_64-linux
where it restores bootstrap (at last :), ok to commit?

We're down to 6 ACATS FAIL on x86_64 and 8 on x86:

http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00654.html
http://gcc.gnu.org/ml/gcc-testresults/2005-07/msg00653.html

common:
18818: cd10002 (run) stream attributes
18819: cdd2a02 (run, works at -O0 everywhere) works with -O2 -fno-tree-sra
22333: c34007p c34007r c45282b (run) spurious discriminant CONSTRAINT_ERROR	

x86 only:
18659: c32001e c64105b c95086b (ICE x86, ppc, ia64, works on x86_64, pass everywhere at -O0) works with -O2 -fno-tree-sra

x86_64 only:
20548: c52103x (run) segfault at runtime on x86_64 and hppa

Laurent

2005-07-12  Richard Kenner  <kenner@vlsi1.ultra.nyu.edu>
	    Laurent GUERBY  <laurent@guerby.net>

	PR tree-optimization/22336
	* function.c (record_block_change): Check for 
	cfun->ib_boundaries_block.


Index: function.c
===================================================================
RCS file: /cvs/gcc/gcc/gcc/function.c,v
retrieving revision 1.635
diff -u -r1.635 function.c
--- function.c  7 Jul 2005 21:04:31 -0000       1.635
+++ function.c  10 Jul 2005 19:06:10 -0000
@@ -5502,6 +5502,9 @@
   if (!block)
     return;

+  if(!cfun->ib_boundaries_block)
+    return;
+
   last_block = VARRAY_TOP_TREE (cfun->ib_boundaries_block);
   VARRAY_POP (cfun->ib_boundaries_block);
   n = get_max_uid ();


On Tue, 2005-07-05 at 10:31 +0200, Laurent GUERBY wrote:
> This is http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22212
> and is the problem blocking Ada bootstrap on x86_64-linux,
> it would be great to move forward on this.
> 
> Laurent
> 
> On Thu, 2005-06-30 at 18:18 -0400, Richard Kenner wrote:
> > This function generates RTL from an expression to see how many RTL insns
> > it is.  But this causes a problem compiling the Ada ACATS test cxa4006.
> > 
> > The problem is when part of the expression has a location.  In that
> > case, record_block_change is called and that relies on
> > cfun->ib_boundaries_block being set.  But it isn't because we aren't
> > expanding stuff "for real".  A kludge would be to test that field, but
> > what's the proper way?
> > 
> > Also, seq_cost really should be looking at next_real_insn, not NEXT_INSN,
> > since any notes shouldn't be counted.
> > 

  reply	other threads:[~2005-07-12 10:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-30 22:16 Problem with tree-ssa-loop-ivopts.c:get_computation-cost Richard Kenner
2005-07-05  8:32 ` Laurent GUERBY
2005-07-12 10:04   ` Laurent GUERBY [this message]
2005-07-12 11:04     ` PR22336 (was: Problem with tree-ssa-loop-ivopts.c:get_computation-cost) Zdenek Dvorak
2005-07-21 22:08     ` Richard Henderson
2005-07-12 13:48 Richard Kenner
2005-07-12 13:55 ` Zdenek Dvorak

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=1121162567.11810.150.camel@m.site \
    --to=laurent@guerby.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=kenner@vlsi1.ultra.nyu.edu \
    /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).