From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 8879 invoked by alias); 28 Jan 2005 17:20:10 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 8804 invoked by uid 48); 28 Jan 2005 17:20:04 -0000 Date: Fri, 28 Jan 2005 17:20:00 -0000 Message-ID: <20050128172004.8803.qmail@sourceware.org> From: "coudert at clipper dot ens dot fr" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041129105735.18714.paul.richard.thomas@cea.fr> References: <20041129105735.18714.paul.richard.thomas@cea.fr> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug fortran/18714] Runtime hang in LAPACK routine SLAMC1 - in Quetzal benchmark suite X-Bugzilla-Reason: CC X-SW-Source: 2005-01/txt/msg04200.txt.bz2 List-Id: ------- Additional Comments From coudert at clipper dot ens dot fr 2005-01-28 17:20 ------- (reply to comments #3 and #4) The print statement in the code induces I/O, which in some sense "disrupt the flow of code" and has the effect of making unaware of possible optimizations. I can't offer a deeper explanation than this statement, only dictated by experience and not actual knowledge of the in-depths of compilers. Removed the "wrong-code" keyword and the blocking of PR18714, since this is actually not a bug. -- What |Removed |Added ---------------------------------------------------------------------------- OtherBugsDependingO|19292 | nThis| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18714