This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: mudflap vs bounds-checking
- From: fche at redhat dot com (Frank Ch. Eigler)
- To: Christophe LYON <christophe dot lyon at st dot com>
- Cc: gcc at gcc dot gnu dot org
- Date: 14 Feb 2007 16:31:02 -0500
- Subject: Re: mudflap vs bounds-checking
- References: <45D32ECF.1040903@st.com>
Christophe LYON <christophe.lyon@st.com> writes:
> What is the difference between the [bounds-checking and mudflap]
> systems?
Mudflap is a tree-level rewriting pass amidst the optimizers that
limits its attention to pointer dereference and addressable object
lifetime events. It's upstream, having been donated to the FSF.
Last time I checked (quite some time back), the bounds-checking code
instrumented many more low-level pointer operations with first-class
function calls, and ran considerably slower as a consequence. It's
not (C) FSF.
Their runtimes are different and probably have different performance
and portability/flexibility/diagnostic capabilities. The development
intensity on both projects appears to have come down since around the
same point in time. It would be nice not to duplicate so much, but
that's how it goes sometimes.
- FChE