public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "P dot Schaffnit at access dot rwth-aachen dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/27392] [4.2 Regression] GCC error: in n_of_executions_at_least, at tree-ssa-loop-niter.c:1772
Date: Wed, 03 May 2006 19:28:00 -0000	[thread overview]
Message-ID: <20060503192835.29747.qmail@sourceware.org> (raw)
In-Reply-To: <bug-27392-276@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from P dot Schaffnit at access dot rwth-aachen dot de  2006-05-03 19:28 -------

Erm... sorry about that, I didn't think about it: I've indeed thrown out a lot
(I do not have the original sources at hand, but they are happily compiled by
quite a few compilers, including lf95, as far as I can tell, is a
reference...): anyway, I thought that the mere fact that *any* code causes an
ICE is bad, I hoped this could help, I'll try to reduce it a bit less
aggressively tomorrow...

Philippe

(In reply to comment #4)
> Phillipe,
> 
> Your code appears to be wrong, or perhaps you've cut down a
> larger code too agressively.  You use the Fortran ALL intrinsic
> on the allocatable NEW_NUMBER, but you have never actually
> allocated memory for the array.
> 
> -- 
> steve 
> 


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27392


  parent reply	other threads:[~2006-05-03 19:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-02 15:23 [Bug middle-end/27392] New: " danglin at gcc dot gnu dot org
2006-05-02 15:29 ` [Bug tree-optimization/27392] " pinskia at gcc dot gnu dot org
2006-05-02 16:43 ` [Bug tree-optimization/27392] [4.2 Regression] " schwab at suse dot de
2006-05-03 11:44 ` P dot Schaffnit at access dot rwth-aachen dot de
2006-05-03 17:11 ` kargl at gcc dot gnu dot org
2006-05-03 19:28 ` P dot Schaffnit at access dot rwth-aachen dot de [this message]
2006-05-03 19:35 ` rakdver at atrey dot karlin dot mff dot cuni dot cz
2006-05-03 19:40 ` dave at hiauly1 dot hia dot nrc dot ca
2006-05-04  9:38 ` P dot Schaffnit at access dot rwth-aachen dot de
2006-05-04 10:50 ` rakdver 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=20060503192835.29747.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).