On Fri, Oct 13, 2006 at 03:24:08PM -0500, Lacefield, Greg (CNS COE) wrote: > However, I need to confirm, in the case of > an FAA audit, that GCC 3.3.1 implements dynamic binding in this fashion. > Can anyone on the steering committee "officially" confirm that GCC uses > static v-tables as described in the ABI?
This would imply that you are asking for some kind of indemnification or binding promise. GCC comes with no warranties of any kind. I can informally and unofficially tell you that GCC uses conventional static virtual function tables and *attempts* to comply with the ABI; I can also tell you that 3.3.x had some bugs in ABI conformance that were fixed in 3.4, so the compliance is not perfect. Also, 3.3.1 is an odd release to choose if you are worrying about quality; four bug fix releases were made to the gcc 3.3.x series after that (the last one was 3.3.5); none of these addressed the ABI problem because of the GCC project's rules for binary compatibility between x.y.z and x.y.(z+1) (again, no warranty on this, but the aim is not to break compatibility). See http://gcc.gnu.org/releases.html for the full history. One possibility is for you to hire a consultant to determine whether the version of gcc that you are using meets your customer's requirements, or assign a staff member to do this job.
