Date: Tue, 26 Apr 2011 11:46:45 -0400 From: David Schultz <das@FreeBSD.ORG> To: Rui Paulo <rpaulo@gmail.com> Cc: "arch@freebsd.org" <arch@FreeBSD.ORG>, "current@freebsd.org" <current@FreeBSD.ORG> Subject: Re: Removal of ICC (intel compiler) bits from mk Message-ID: <20110426154645.GA67273@zim.MIT.EDU> In-Reply-To: <E604222D-A731-4F0E-BF21-FF7F4306A899@gmail.com> References: <E604222D-A731-4F0E-BF21-FF7F4306A899@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, Aug 18, 2010, Rui Paulo wrote: > Hi, > I've been chatting with the ICC ex-users and they seem to be ok with the removal of the ICC bits from share/mk and other places. > The reason is that it doesn't work and no one has volunteered to fix it for many years. This seems to indicate that the interest in ICC is low. > If there's anyone against this, speak now or forever be silent. :-) For what it's worth, I still occasionally use icc for simple tasks-- mainly as a reference for code generation, since it produces reasonable output in many cases where gcc does not. As I recall, making it work required minimal changes... possibly just making sure __va_list gets defined in _types.h. I have the following in one of my trees, although this is obviously not the right fix. Index: _types.h =================================================================== --- _types.h (revision 219357) +++ _types.h (working copy) @@ -105,7 +105,7 @@ */ #ifdef __GNUCLIKE_BUILTIN_VARARGS typedef __builtin_va_list __va_list; /* internally known to gcc */ -#elif defined(lint) +#else typedef char * __va_list; /* pretend */ #endif #if defined(__GNUC_VA_LIST_COMPATIBILITY) && !defined(__GNUC_VA_LIST) \
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20110426154645.GA67273>