On Wed, 23 Feb 2005, Doug Graham wrote:
Regarding memory consumption, perhaps libmudflap's default backtrace
parameter should be set to zero, for both speed and space reasons.
If it's storing all the backtraces that is burning up all the memory,
another approach might be to keep a separate hash tab
> I think the decision to force the
> user to specify -lmudflap should be revisited.
This is already in bugzilla see:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18885
#Michael Cieslinski
On Wed, 2005-02-23 at 09:49, Frank Ch. Eigler wrote:
> You should not have to invent any further static counters
> for this stuff: the __mf_state variable should be able to do the right
> thing.
Thanks for the helpful comments. The __mf_state variable does indeed
look like it can cleanly solve th
On Wed, 2005-02-23 at 01:00, Paolo Bonzini wrote:
> > The fixincludes Makefile.in does not use CFLAGS when linking.
> I think this can be committed as obvious, especially by a GWP person as
> you are...
I'll be taking care of this today. I don't like to rely on the obvious
rule, and it was rathe
On Wed, Feb 23, 2005 at 12:49:41PM -0500, Frank Ch. Eigler wrote:
> Regarding memory consumption, perhaps libmudflap's default backtrace
> parameter should be set to zero, for both speed and space reasons.
If it's storing all the backtraces that is burning up all the memory,
another approach might
On Wed, Feb 23, 2005 at 12:49:41PM -0500, Frank Ch. Eigler wrote:
> Regarding -fmudflap => -lmudflap, it used to do that. The problem was
> that the simplest use of specs machinery creates a final sequence of
> "-lFOO" options that sometimes cannot work. libmudflap must be in a
> particular spot
Hi, Jim -
> A customer expressed interest in mudflap, so I tried to see if I
> could use it compile something large. [...]
Thanks for giving it a try.
For what it's worth, I've run entire gcc bootstraps on Linux with the
instrumentation running (using BOOT_CFLAGS rather than CFLAGS). Each
ti
I think the decision to force the
user to specify -lmudflap should be revisited.
I agree.
The fixincludes build failed with link errors for undefined mudflap
functions. The fixincludes Makefile.in does not use CFLAGS when linking. I
added $(CFLAGS) to the 3 rules that contain a link command.
I th
A customer expressed interest in mudflap, so I tried to see if I could
use it compile something large. I used gcc itself for this test. I've
attached my notes, and the patches I wrote as part of this. I will
probably be able to generate a couple of bug reports and/or patches out
of this.
--
Jim
