Date: Thu, 13 Feb 1997 21:39:15 -0500 From: "David S. Miller" <davem@jenolan.rutgers.edu> To: karpen@ocean.campus.luth.se Cc: hamby@aris.jpl.nasa.gov, hackers@freebsd.org Subject: Re: Sun Workshop compiler vs. GCC? Message-ID: <199702140239.VAA04018@jenolan.caipgeneral> In-Reply-To: <199702140004.BAA03489@ocean.campus.luth.se> (message from Mikael Karpberg on Fri, 14 Feb 1997 01:04:54 %2B0100 (MET))
next in thread | previous in thread | raw e-mail | index | archive | help
From: Mikael Karpberg <karpen@ocean.campus.luth.se> Date: Fri, 14 Feb 1997 01:04:54 +0100 (MET) Speaking of CC and g++... At work we use CC, and I'm getting fairly used to templates, WORKING exceptions (WOW! Who ever heard of such a thing?), and all the thread thingies, like mutexes, etc, default Just Working. So... Does anyone know when g++ will handle this? Would be SO nice to have at home too, for the pet projects. 2.8.0 will have what you describe. In fact completely generic exception code generation has been added to gcc's backend. This means the target specific code for exception generation can be shared between the ADA and C++ frontends. In fact the new exception mechanism allows you to compile a normal C library which is exception aware. For example, this lets a throw propagate properly back through a call to qsort() in libc. ---------------------------------------------//// Yow! 11.26 MB/s remote host TCP bandwidth & //// 199 usec remote TCP latency over 100Mb/s //// ethernet. Beat that! //// -----------------------------------------////__________ o David S. Miller, davem@caip.rutgers.edu /_____________/ / // /_/ ><
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199702140239.VAA04018>