From:	dumser AT ti DOT com (James Dumser)
Subject:	Re: printf and long long
29 Apr 1997 12:48:48 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<199704291618.LAA03104.cygnus.gnu-win32@lesol1.dseg.ti.com>
Mime-Version:	1.0
Original-To:	marc AT watson DOT ibm DOT com
Original-Cc:	gnu-win32 AT cygnus DOT com
In-Reply-To:	<9704281509.AA31696@marc.watson.ibm.com> from "Marc Auslander" at Apr 28, 97 11:09:32 am
X-MIMI-Options:	headers none
X-Mailer:	ELM [version 2.4 PL23]
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

On Mon, 28 Apr 1997 11:09:32 -0400, you Marc Auslander
  <marc AT watson DOT ibm DOT com> wrote:
>My problem is with gcc cygnus-2.7.2-961023 running on Windows 95.  I
>have no problem with gcc 2.7.2.1 on AIX, for example.  It appears from
>your note that you tried a BSD gcc, and it also works.
>
>By the way, according to the gnu libc info, q is the BSD name for ll,
>and the libaray in fact supports ll, L and q as synonyms.

And there lies the problem. cygwin32 does not use the GNU libc library
(if they did, they would not be able to require people to buy a license
from them to keep from releasing their source code). Instead, it uses
"newlib," with the source for the functions in question
(printf->vfprintf)
  Copyright (c) 1990 The Regents of the University of California.
  All rights reserved.

Looking at the code, l is long ints, L is for long doubles, ll is
supposed to be for long long ints (QUADINTs), and q is also for long
long ints. If things are not working like this, you'll need to take a
look at cdk/src/newlib/stdio/vfprintf.c to attempt to find the
problem.

-- 
James Dumser    972-462-5335 dumser AT ti DOT com
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -