X-Spam-Check-By: sourceware.org Message-ID: <46B0FDEB.401BFCA0@dessent.net> Date: Wed, 01 Aug 2007 14:40:59 -0700 From: Brian Dessent X-Mailer: Mozilla 4.79 [en] (Windows NT 5.0; U) MIME-Version: 1.0 To: cygwin@cygwin.com Subject: Re: printf References: <46B0C457.4A512ECF@dessent.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Reply-To: cygwin@cygwin.com Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com "Frederich, Eric P21322" wrote: > Do vfprintf statements compiled on Cygwin go through libiberty which > then calls fprintf, or is there another vfprintf in whatever C library > I'm linking against (either Cygwin's or Microsoft's)? No, you're getting confused by libiberty. It is used internally *in* gcc as a portability aide for gcc itself. When you call printf in a Cygwin program, the implementation is in cygwin1.dll, and Cygwin implements this internally via newlib. Look at the Cygwin source (which includes the newlib source) if you want to see how it's implemented, not the gcc source. Brian -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/