From: <dan...@ya...> - 2002-06-12 04:04:13
|
Earnie, I have a set of new long double (and some C99 float and double) math almost ready to be checked into mingwex. This will give idea of the functions. New files are: ? mingwex/acoshl.c ? mingwex/acosl.c ? mingwex/asinhl.c ? mingwex/asinl.c ? mingwex/atan2l.c ? mingwex/atanhl.c ? mingwex/atanl.c ? mingwex/ceill.S ? mingwex/cosl.S ? mingwex/expl.c ? mingwex/fabs.c ? mingwex/fabsf.c ? mingwex/fabsl.c ? mingwex/floorl.S ? mingwex/fmodl.c ? mingwex/log10.S ? mingwex/log10f.S ? mingwex/log10l.S ? mingwex/log2.S ? mingwex/log2f.S ? mingwex/log2l.S ? mingwex/logbl.c ? mingwex/logl.S ? mingwex/modfl.c ? mingwex/nearbyint.S ? mingwex/nearbyintf.S ? mingwex/nearbyintl.S ? mingwex/remainder.S ? mingwex/remainderf.S ? mingwex/remainderl.S ? mingwex/remquo.S ? mingwex/remquof.S ? mingwex/remquol.S ? mingwex/sinl.S ? mingwex/sqrtl.c ? mingwex/tanl.S These are mostly based on PD code by J.T. Conklin <jt...@ne...>. I have tested these and am happy, but have not yet gone through and checked whether the "special cases" of out-of-range zeroes, NaNs, Infs (eg, logl(1.0L/0.0L)) return the same as MSVC double versions. The standard allow "implementation" specific retrns for many of these special cases. You mentioned earlier about a pending merge of mingwex to trunk. If so, should I consider branch frozen and leave these till after the merge. Or should I check in now. I am working on long double capable *printf, based on Cephes code targeted as a patch for DJGPP, but that needs a lot more work. Danny http://www.sold.com.au - SOLD.com.au - Find yourself a bargain! |
From: Earnie B. <ear...@ya...> - 2002-06-12 12:02:58
|
Danny Smith wrote: > > Earnie, > I have a set of new long double (and some C99 float and double) math almost > ready to be checked into mingwex. > ->8- > > You mentioned earlier about a pending merge of mingwex to trunk. If so, should > I consider branch frozen and leave these till after the merge. Or should I > check in now. > Go ahead and check into branch. Hmm... It sounds as if I was waiting on you and you were waiting on me wrt merge to trunk. Why don't you merge to trunk first then you can upload to branch. Once the merge is done I'll create an official release. > I am working on long double capable *printf, based on Cephes code targeted as a > patch for DJGPP, but that needs a lot more work. > Perhaps using http://www.ijs.si/software/snprintf/ as the base for *printf? It's license is a modified Artistic license. You might also consider newlib's reentrant *printf implementation, it's license is file based, PD, BSD, etc but no GPL or LGPL. Earnie. |
From: Danny S. <dan...@cl...> - 2002-06-12 22:01:52
|
----- Original Message ----- From: "Earnie Boyd" <ear...@ya...> To: <min...@li...> Sent: Thursday, 13 June 2002 00:00 Subject: Re: [MinGW-dvlpr] mingwex - more long double math functions > Danny Smith wrote: > > > > Earnie, > > I have a set of new long double (and some C99 float and double) math almost > > ready to be checked into mingwex. > > > ->8- > > > Go ahead and check into branch. Hmm... It sounds as if I was waiting > on you and you were waiting on me wrt merge to trunk. Why don't you > merge to trunk first then you can upload to branch. Once the merge is > done I'll create an official release. OK, when I have time I will merge current mingwex to trunk. Then I will check in new files to branch. I think that is what you mean. This will not happen until I do some more reading about merging branches. Also the current crap on mingw list about long double tempts me to give up.... > > > I am working on long double capable *printf, based on Cephes code targeted as a > > patch for DJGPP, but that needs a lot more work. > > > > Perhaps using http://www.ijs.si/software/snprintf/ as the base for > *printf? It's license is a modified Artistic license. > Actually there are quite of few *printf's around. The difficult part with all of them is thread safety and sync of standard streams Getting ld support for printf is about 133 on my TODO list. Its not that important to me. The only time I would use it is to debug math functions, but its actually better to use hex representaion of the words in a long double. So if anyone thinks it is important, do it. > You might also consider newlib's reentrant *printf implementation, it's > license is file based, PD, BSD, etc but no GPL or LGPL. OK > > Earnie. > > _______________________________________________________________ > > Sponsored by: > ThinkGeek at http://www.ThinkGeek.com/ > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
From: Earnie B. <ear...@ya...> - 2002-06-13 00:06:17
|
--- Danny Smith <dan...@cl...> wrote: > > ----- Original Message ----- > From: "Earnie Boyd" <ear...@ya...> > To: <min...@li...> > Sent: Thursday, 13 June 2002 00:00 > Subject: Re: [MinGW-dvlpr] mingwex - more long double math functions > > > > Danny Smith wrote: > > > > > > Earnie, > > > I have a set of new long double (and some C99 float and double) > math almost > > > ready to be checked into mingwex. > > > > > ->8- > > > > > Go ahead and check into branch. Hmm... It sounds as if I was waiting > > on you and you were waiting on me wrt merge to trunk. Why don't you > > merge to trunk first then you can upload to branch. Once the merge is > > done I'll create an official release. > > OK, when I have time I will merge current mingwex to trunk. Then I will > check in new files to branch. > I think that is what you mean. This will not happen until I do some > more reading about merging branches. Yes, that is what I meant. > Also the current crap on mingw list about long double tempts me to give > up.... > Hang, in there. If it gets to you, you've just got to ignore it. People will always complain and give ill advice without much more input thinking it will help drive their case when all it does in reality is disgust those doing the work. > > > > > I am working on long double capable *printf, based on Cephes code > targeted as a > > > patch for DJGPP, but that needs a lot more work. > > > > > > > Perhaps using http://www.ijs.si/software/snprintf/ as the base for > > *printf? It's license is a modified Artistic license. > > > Actually there are quite of few *printf's around. The difficult part > with all of them is thread safety and sync of standard streams > > Getting ld support for printf is about 133 on my TODO list. Its not > that important to me. The only time I would use it is to debug math > functions, but its actually better to use hex representaion of the words > in a long double. > So if anyone thinks it is important, do it. > Yep, doubt that it will be me. Earnie. ===== Earnie Boyd mailto:ear...@ya... --- <http://earniesystems.safeshopper.com> --- --- Cygwin: POSIX on Windows <http://gw32.freeyellow.com/> --- --- Minimalist GNU for Windows <http://www.mingw.org/> --- __________________________________________________ Do You Yahoo!? Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com |
From: Danny S. <dan...@cl...> - 2002-06-14 00:34:49
|
> > > Danny Smith wrote: > > > > > > Earnie, > > > I have a set of new long double (and some C99 float and double) > math almost > > > ready to be checked into mingwex. > > > > > ->8- > > > > > Go ahead and check into branch. Hmm... It sounds as if I was waiting > > on you and you were waiting on me wrt merge to trunk. Why don't you > > merge to trunk first then you can upload to branch. Once the merge is > > done I'll create an official release. > > OK, when I have time I will merge current mingwex to trunk. Then I will > check in new files to branch. I've merged in mingwex to trunk. I'm wondering why we still need to maintain branch. The concept being tested in the mingwex branch has been admitted into trunk, so its distinction as a branch is now no longer clear. I realize that checking in the 30 odd new files that I mentioned earlier to trunk carries risk, but it also keeps things simpler and means that we need to produce only trunk snapshots to get changes/additions exercised by users. Would it be acceptable for me to just wait for ming-runtime-2.0 release before checking new additions into _trunk_, rather than checking in additions to mingwex branch now and then merging those additions back into trunk in a few months?. Danny |
From: Earnie B. <ear...@ya...> - 2002-06-14 10:23:08
|
Danny Smith wrote: > > I've merged in mingwex to trunk. I'm wondering why we still need to > maintain branch. Great minds must think alike, we don't. However, I would like to produce a mingw-runtime-2.0 release before you add anything new. > The concept being tested in the mingwex branch has been admitted into > trunk, so its distinction as a branch is now no longer clear. I realize > that checking in the 30 odd new files that I mentioned earlier to trunk > carries risk, but it also keeps things simpler and means that we need to > produce only trunk snapshots to get changes/additions exercised by > users. > > Would it be acceptable for me to just wait for ming-runtime-2.0 release > before checking new additions into _trunk_, rather than checking in > additions to mingwex branch now and then merging those additions back > into trunk in a few months?. > Yes. I'll try to get out a release canidate this weekend. I'll be working and will have lots of spare cycles so it should be possible. Earnie. P.S.: I don't see the notification of the CVS changes for the merge to HEAD. |
From: Earnie B. <ear...@ya...> - 2002-06-14 10:37:20
|
Earnie Boyd wrote: > > > P.S.: I don't see the notification of the CVS changes for the merge to > HEAD. > Ignore, I just found it. Earnie. |
From: Casper H. <ch...@it...> - 2002-06-14 17:05:48
|
When building the binutils package (linked to below) on a Mandrake 8.1, I get a missing symbol (stricmp) error. The patch below fixes the problem. I assume it is a typo since all other other string comparisons to ex->string are case sensitive. Is this a correct assumption? http://prdownloads.sourceforge.net/mingw/binutils-2_12_90-20020518-1-src.tar.gz?download Casper --- pe-dll.c.compare Fri Jun 14 14:46:29 2002 +++ pe-dll.c Fri Jun 14 14:45:25 2002 @@ -514,7 +514,7 @@ { if (libname && ((strcmp (libname, ex->string) == 0) - || (stricmp ("ALL", ex->string) == 0))) + || (strcmp ("ALL", ex->string) == 0))) return 0; } else if (strcmp (n, ex->string) == 0) |
From: Casper H. <ch...@it...> - 2002-06-15 00:00:53
|
When building the binutils package (linked to below) on a Mandrake 8.1, I get a missing symbol (stricmp) error. The patch below fixes the problem. I assume it is a typo since all other other string comparisons to ex->string are case sensitive. Is this a correct assumption? http://prdownloads.sourceforge.net/mingw/binutils-2_12_90-20020518-1-src.tar.gz?download Casper --- pe-dll.c.compare Fri Jun 14 14:46:29 2002 +++ pe-dll.c Fri Jun 14 14:45:25 2002 @@ -514,7 +514,7 @@ { if (libname && ((strcmp (libname, ex->string) == 0) - || (stricmp ("ALL", ex->string) == 0))) + || (strcmp ("ALL", ex->string) == 0))) return 0; } else if (strcmp (n, ex->string) == 0) |
From: Danny S. <dan...@cl...> - 2002-06-14 22:33:48
|
> > > > Yes. I'll try to get out a release canidate this weekend. I'll be > working and will have lots of spare cycles so it should be possible. > Thanks > Earnie. > > P.S.: I don't see the notification of the CVS changes for the merge to > HEAD. > Sorry. I was waiting on decision on future of mingwex branch. If it is going to continue, I thought a new tag would be helpful to make future merges easier. Does that mean just a ChangeLog entry in mingwex branch with message, or should I still retag the branch as well?. Danny > ____ ___________________________________________________________ > > Don't miss the 2002 Sprint PCS Application Developer's Conference > August 25-28 in Las Vegas - http://devcon.sprintpcs.com/adp/index.cfm?source=osdntextlink > > _______________________________________________ > MinGW-dvlpr mailing list > Min...@li... > https://lists.sourceforge.net/lists/listinfo/mingw-dvlpr |
From: Danny S. <dan...@cl...> - 2002-06-14 22:36:15
|
----- Original Message ----- From: "Casper Hornstrup" <ch...@it...> To: <min...@li...> Sent: Saturday, 15 June 2002 04:16 Subject: [MinGW-dvlpr] Building binutils fails > When building the binutils package (linked to below) on a Mandrake 8.1, I get a > missing symbol (stricmp) error. The patch below fixes the problem. > I assume it is a typo since all other other string comparisons to ex->string are case sensitive. Is this a correct assumption? > It's been fixed in official binutils CVS (Chris Faylor changed my non-portable stricmp to strncasecmp when he committed my changes) Danny |
From: Earnie B. <ear...@ya...> - 2002-06-15 12:12:26
|
Danny Smith wrote: > > > > > P.S.: I don't see the notification of the CVS changes for the merge to > > HEAD. > > > > Sorry. I was waiting on decision on future of mingwex branch. I meant from the cygwin-cvs list. > If it is > going to continue, I thought a new tag would be helpful to make future > merges easier. > Not need to continue the branch. > Does that mean just a ChangeLog entry in mingwex branch with message, or > should I still retag the branch as well?. > No need for this either. Earnie. |
From: Earnie B. <ear...@ya...> - 2002-06-15 16:03:40
|
Danny Smith wrote: > > > > > > > > Yes. I'll try to get out a release canidate this weekend. I'll be > > working and will have lots of spare cycles so it should be possible. > > > Thanks > You're welcome. Release complete, minor version has be incremented. Add your files to the HEAD. Earnie. |