X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Mon, 15 Feb 2010 17:15:37 +0100
From: Corinna Vinschen <corinna-cygwin AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: [gcc] FYI, libffi FAILs with cygwin snapshot 20100205,    20100207 &   20100210...
Message-ID: <20100215161537.GB5683@calimero.vinschen.de>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <20100215085727 DOT GT5683 AT calimero DOT vinschen DOT de>  <414831 DOT 65632 DOT qm AT web25503 DOT mail DOT ukl DOT yahoo DOT com>  <20100215141518 DOT GZ5683 AT calimero DOT vinschen DOT de>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20100215141518.GZ5683@calimero.vinschen.de>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
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 Feb 15 15:15, Corinna Vinschen wrote:
> On Feb 15 10:18, Marco Atzeri wrote:
> > I hope it can help
> 
> Thanks, but that's not exactly "simple".  It requires to run a test
> through an interpreter.  It would still be more helpful to get a simple
> testcase in plain C or at least just the regular expression and the
> string it stumbles over.  I would have to to the same, so I hoped that
> somebody else would at least help to skip the preliminary steps, so I
> can concentrate on actual debugging and fixing.

Probably I found the culprit.  I introduced a bug in vfprintf when I
added thousands separator printing.  The result of the bug is that float
or double values got an extra decimal point.  The float value 1 got
printed as "1.", for instance.  I don't know how this relates to the
autom4ate case, but it should at least fix the libffi issue.  This
should show up in the next developer's snapshot.


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader          cygwin AT cygwin DOT com
Red Hat

--
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