Mail Archives: djgpp-workers/2001/12/02/07:14:12
Hello.
Martin Stromberg wrote:
> > Are there any plans to build a package containing the profiling
> > version of the library for 2.04 - a djpro204.zip containing libc_p.a,
> > for instance? Has there been much demand for a profiling version of
> > 2.03? (I'm guessing that there hasn't.)
>
> Well I'd like that. Preferably so the profiling version of libc.a
> could be decided by a command line option (or something equivalent).
I think we'd have to update our specs file. egcs on RH Linux 6.2 has the
following in its specs file:
*lib:
%{shared: -lc --version-script libgcc.map%s} %{!shared:
%{mieee-fp:-lieee} %{pthread:-lpthread} %{profile:-lc_p} %{!profile:
-lc}}
Our specs file from gcc 3.0.2 just has:
*lib:
-lc
> Do your profiling patches build a libc_p.a, (I can't test build libc.a
> right now.) so we get both a normal and a profile enabled libc?
No, the patches allow you to build a profiled version of libc by tweaking
the options in src/gcc.opt. Previously libc compiled with profiling would
cause programs compiled against it to crash. The reason was that the
profiling support was compiled with profiling, which lead to unlimited
recursion in the profiling support code.
The build system would need more invasive modifications to support
building two different sets of objects for the two libraries. We could
then fix the problem with libemu cleanly - link it against normal libc.
BTW I've just committed the profiling patches.
Thanks, bye, Rich =]
--
Richard Dawe
http://www.phekda.freeserve.co.uk/richdawe/
- Raw text -