Path: utzoo!mnetor!uunet!lll-winken!lll-tis!ames!umd5!brl-adm!brl-smoke!gwyn
From: gwyn@brl-smoke.ARPA (Doug Gwyn )
Newsgroups: comp.lang.c
Subject: Re: Modula2's godawful IO.
Message-ID: <7749@brl-smoke.ARPA>
Date: 24 Apr 88 16:44:12 GMT
References: <764@ndsuvax.UUCP> <535@m10ux.UUCP> <730@mhuxm.UUCP> <942@unmvax.unm.edu> <230@jupiter.olyis.UUCP>
Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB) <gwyn>)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 10

In article <230@jupiter.olyis.UUCP> ecb@pluto.UUCP (Eric Brown) writes:
>In article <942@unmvax.unm.edu> mike@turing.UNM.EDU.UUCP (Michael I. Bushnell) writes:
>>Go ahead and use printf.  It doesn't really cost you that much.
>Now include the size of the floating point libraries.

Sounds to me like to need to have a little talk with your compiler vendor.
There is no need to link floating-point support into the process image
when the application has made no use of floating point.  Even the old PDP-11
UNIX got this right -- there were two _doprnt entries in the library, one for
use with floating-point and one without; the choice was tied to whether or
not the compiler had generated a ".fltused" reference.