Date: Sun, 31 Jan 2016 17:49:56 +0100 From: Szabolcs Nagy <nsz@...t70.net> To: Alba Pompeo <albapompeo@...il.com> Cc: musl@...ts.openwall.com Subject: Re: Julia on musl libc systems * Alba Pompeo <albapompeo@...il.com> [2016-01-30 23:13:48 -0200]: > Good to know more about the historical development and different > technical features of both libm implementations. Maybe musl and julia > developers could set up a discussion in the near future to see how > they can minimize duplicated efforts. > > Mr. Nagy, we finally came across an issue that may need an experts > help. Could you have a look at it? added the musl list into cc, musl specific issues should be discussed there > It's one of musl dependencies (suitesparse). > It's an off-putting issue, but I hope it's fixable. An internal compiler error. > https://github.com/tkelman/julia-alpine/issues/1#issuecomment-177282137 > The .c file in question is here. > https://github.com/jluttine/suitesparse/blob/master/CHOLMOD/Modify/t_cholmod_updown_numkr.c > if an unstable version of the clang preprocessor crashes with ice, it is probably not libc related. but others who use clang with musl might know about this (i'd try to reduce the example and report the error against clang) > On Sat, Jan 30, 2016 at 11:07 PM, Szabolcs Nagy <nsz@...t70.net> wrote: > > * Alba Pompeo <albapompeo@...il.com> [2016-01-30 20:08:55 -0200]: > >> I've been looking more deeply into Julia's dependencies and found this. > >> https://github.com/JuliaLang/openlibm > >> Isn't the purpose of openlibm exactly that of musl's libm? > > > > i think openlibm got forked off from freebsd libm > > around the same time as musl libm did. > > > > the goals are slightly different i think > > > > musl libm cleaned up more historical c programming > > issues and is tuned for libc use. > > > > openlibm probably has more performance/precision > > tunings and it is for portable behaviour across > > different platforms. > > > >> This seems like a huge duplicated effort in my view. > >> Couldn't Julia devs simply use musl's libm and be done with it or am I > >> missing something here? > > > > they would have to cut math out of the musl > > source tree and make some os specific changes > > (default fenv setup on i386 etc.) > > > > it would be nice to work together, most of the > > code can be shared, but some of the surrounding > > build system probably not.
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.