X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-bounces using -f
From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Alignment problem
Date: Sun, 10 Feb 2002 00:52:44 CST
Organization: Rice University, Houston TX
Lines: 34
Message-ID: <3c6618bc.sandmann@clio.rice.edu>
References: <3C650C18 DOT B45F67D4 AT yahoo DOT com> <4331-Sat09Feb2002145741+0200-eliz AT is DOT elta DOT co DOT il> <3C655E12 DOT 6F8D351E AT yahoo DOT com> <200202091859 DOT g19Ixam19704 AT envy DOT delorie DOT com> <3C6586A1 DOT C3AE5AC3 AT yahoo DOT com> <200202092259 DOT g19MxQP21308 AT envy DOT delorie DOT com> <3C65EDB7 DOT 4098CC7 AT yahoo DOT com>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1013324570 7643 128.42.105.3 (10 Feb 2002 07:02:50 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 10 Feb 2002 07:02:50 GMT
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> DJ Delorie wrote:
> > 
> > Make sure malloc.c is including xmalloc.h from the libc source, not
> > some other xmalloc, and that it has access to <libc/malloc.h>.
> 
> Now what is this?  There is no xmalloc.h reference in the malloc
> source?  There is no xmalloc.h on my system.

Ignore this advice unless you download the V2.04 work in progress from
CVS.  xmalloc.h is part of the restructured malloc (new) but is not used
or needed by the V2.03 source version.

> Would you please go back to my previous post and answer the
> specific questions, which I requote below:
> 
> "however the same command seems to function if I eliminate the -W
> -Wall -ansi -pedantic -gstabs+ default flags by using *gcc.  

These are not default flags in GCC.  (I don't know where these are
coming from?  Are you using a command line or ?).  You don't actually 
need any of them (and some may be causing the compile problems).  
Something like gcc -c -O2 -pg malloc.c should do it.

> ... Obviously the only portion that needs profiling
> is the malloc.c content, and that should be as detailed as
> possible. Should I be using gstabs+, gstabs, or g?  The other
> modules are compiled with the defaults above.  Does that matter?"

It doesn't matter.  Since malloc.c is not C++ you don't gain much
from the extra debugging info.  We really are looking for profile
information here.

Thanks.