Date: Mon, 15 Mar 2004 19:46:32 -0500 From: Chuck Swiger <cswiger@mac.com> To: Adam Bozanich <abozan01@ccsf.edu> Cc: questions@freebsd.org Subject: Re: [OT?] write C program with UTF16LE Message-ID: <40564E68.9060101@mac.com> In-Reply-To: <Pine.HPX.4.44.0403151423290.997-100000@hills.ccsf.cc.ca.us> References: <Pine.HPX.4.44.0403151423290.997-100000@hills.ccsf.cc.ca.us>
next in thread | previous in thread | raw e-mail | index | archive | help
Adam Bozanich wrote: > On Mon, 15 Mar 2004, Matthew Seaman wrote: >>Errr... no. Not even if you're using the Linux devtools to create a >>Linux executable. You're using the FreeBSD system libc. Same API, >>different code, different licencing terms. > > Yep, one look at /usr/include/stdio.h proves you right. Thanks... I (obviously) > didn't realize that. > > Now I'm very curious. If BSD has it's own C api, did it at one time have > it's own compiler? If so, what happened to it? Well, one can track down the original C compiler written by Kernighan & Ritchie. Somewhere around 1981, one can also find references to PCC, the "Portable C Compiler" by Aho & Johnson, which has largely been replaced by GNU's gcc since then. There's been some effort recently to make FreeBSD go using Intel's icc, as well. > Does gcc have to know about the different syscall calling conventions? GCC has to know about the local architecture's calling conventions. GCC does not need to know anything special about the system call interface defined by the kernel and libc. -- -Chuck
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?40564E68.9060101>