Mail Archives: djgpp/2015/05/01/04:58:28
On 04/28/2015 08:18 PM, DJ Delorie wrote:
> Ah, I see.
>
> I see no reason to not spin a 2.05 release just to get this out, but
> the only other issue we've had stopping this is the malloc one. IIRC
> the last concern I had with changing malloc was breaking the ABI, but
> if Juan and Andris can agree on what malloc "works" we'll just go with
> that and have something that can replace both 2.03 and 2.04.
>
>
I have updated nmalloc (sorry for 2 missing headers accidentally left out of first commit),
I also restored src/rmake.cc (missing since v2.02) but used by testsuite. Could it really be true
that nobody have dries to build testsuite for so long time.
Also some other changes like adding make variables EXTRA_CLAGS and EXTRA_CXXFLAGS so that extra
flags are visible in make output. Used this to workaround cmalloc() problem (GCC-5.1 compiles it to
infinite tail recursion at optimization levels 2+).
So library now seems to build OK. Should do some more testing with real software.
I guess we'll need version v2.05 in beta for some time before releasing it as current
Problems:
math,.h:
sincos() has different prototype from GCC builtin and also procedure with same name in glibc. It is
however GNU extension. Both changing API and leaving it as we have have different disadvantages. I
do not think sincos() is very widely used, so I would vote for changing prototype
GCC headers (lib/gcc/5.10/include):
does not work nicely with -Wqual-cast. I'll m also getting other warnings like uninitialized
variable from SSE functions but only when building DJGPP test-suite.
testsuite: there are tests for memory allocation debugging which of course no more buiolds after
change to nmalloc.
Otherwise: DJGPP v2.04 CVS version build process works nicely with gcc-5.1.0 (same build that is
uploaded) except for problems with testsuite.
Andris
- Raw text -