X-Recipient:	archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status:	No, hits=-2.3 required=5.0 tests=AWL,BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,TW_BG,T_TO_NO_BRKTS_FREEMAIL
X-Spam-Check-By:	sourceware.org
MIME-Version:	1.0
In-Reply-To:	<AANLkTikrUJjyuQZ_ydKaR5GojGOp3h32ndozatN=qtV=@mail.gmail.com>
References:	<AANLkTikw5F9-M=4Cw9HuGBFUoF2uYUWyOgeosD5STUSw AT mail DOT gmail DOT com> <20110326094551 DOT GF24762 AT calimero DOT vinschen DOT de> <AANLkTinv0j=WGG8g3y2AMg2Qm275BAB9kW8tw37bLcdf AT mail DOT gmail DOT com> <1301200498 DOT 2520 DOT 6 DOT camel AT YAAKOV04> <AANLkTikoRWgTdjyKvqCiMCZXrzFkdWt4rcXsgjbXWMNc AT mail DOT gmail DOT com> <1301213705 DOT 2520 DOT 12 DOT camel AT YAAKOV04> <AANLkTikrUJjyuQZ_ydKaR5GojGOp3h32ndozatN=qtV=@mail.gmail.com>
Date:	Tue, 29 Mar 2011 23:37:08 +0200
Message-ID:	<AANLkTikqwzw9TyYxKiC01axWAOj62pk8DTW2fXCU=WpF@mail.gmail.com>
Subject:	Re: libgfortran3 respin : status and problem
From:	marco atzeri <marco DOT atzeri AT gmail DOT com>
To:	cygwin AT cygwin DOT com
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id:	<cygwin.cygwin.com>
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

On Sun, Mar 27, 2011 at 1:43 PM, marco atzeri  wrote:
> On Sun, Mar 27, 2011 at 10:15 AM, Yaakov (Cygwin/X) wrote:
>> On Sun, 2011-03-27 at 07:43 +0200, marco atzeri wrote:
>>> which lapack ? 3.2.2-1 of distro ?
>>
>> 3.2.2 rebuilt with cygwin 1.7.8 and Ports' gcc 4.5.2-2.
>>
>>
>> Yaakov
>>
>
> Thanks,
> I start to think that there is a problem in lapack-3.2.2.-2 built with
> gcc-4.3.4-4.
>
> It looks that slartg never returns; I need to further dig.
>
> Marco

I guess I catched.
There is likely an optimization bomb that never exploded before during
lapack building.
For what ever reason  gcc-4.3.4-4 activates it and all the previous version not.

slamch.f and dlamch.f could fall in never ending loop if the
optimization is active.
The funny thing is that they were created in such a way to fool
optimization to recover hardware real data.

So at the end it is a PEBCAK problem from the first time that I
adopted lapack and used automake/autoconf.

Marco

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

- Raw text -