|
From: | grischka |
Subject: | Re: [Tinycc-devel] Re : Re: Re : Re: win32: -Wl,-nostdlib: undefined symbol 'memset' |
Date: | Tue, 12 Sep 2023 11:43:55 +0200 |
User-agent: | Mozilla/5.0 (Windows NT 6.0; rv:38.0) Gecko/20100101 Thunderbird/38.5.0 |
On 12.09.2023 11:01, avih via Tinycc-devel wrote:
Tcc does not guarantee to compile pure C code into pure machine code, and any pure-C implementation which the user provides might end up depending on those functions involuntarily. The user has no control..
How do you define "pure C code"? printf is pure (ANSI) C, no? And were did you get that that a compiler should be able to produce runnable binaries from such "pure C" without calling into any library functions? Also, what is "pure machine code"? With neither input nor output it couldn't do anything but waste instruction cycles. -- gr
- avih
[Prev in Thread] | Current Thread | [Next in Thread] |