At least for VAC6, they're all the same binary, but the invocation affects behavior. By default xlc and friends are more ANSI-like, though Parrot shouldn't care. Using cc_r in hints is fine if it matters to you; I didn't pick xlc_r for any particular reason. I was even able to get away with using plain cc with -lpthread, but cc_r is safer. Someone more familiar with AIX and VAC might know what's guaranteed to be there (e.g. if VAC isn't installed).
Adam > -----Original Message----- > From: Nicholas Clark [mailto:[EMAIL PROTECTED] Behalf Of Nicholas > Clark > Sent: Tuesday, March 16, 2004 12:28 PM > To: Jarkko Hietaniemi > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: aix - cc_r vs xlc_r > > > On Tue, Mar 16, 2004 at 10:23:34PM +0200, Jarkko Hietaniemi wrote: > > Nicholas Clark wrote: > > > > > On AIX, what's the difference between cc_r and xlc_r? > > > > See /etc/xlc.cfg. > > > > I vaguely remember that's it's the cc_r that's guaranteed > (well, *more* > > guaranteed) to be there, if there's any compiler with reentrant > > libraries. > > Which would suggest that parrot's hints files should (could?) > be changed to > order the use of cc_r, rather than its current choice of xlc_r ? > > Nicholas Clark >
