[m-dev.] Upgrading Boehm GC, attempt #2

Nick Rudnick nick.rudnick at gmail.com
Tue Jan 20 21:18:48 AEDT 2015


Dear all,

now I can't resist – as I see you are occupied so eagerly with Boehm GC,
are you aware knowledge about Boehm GC it is interesting for amalgamating
Mercury with other software? Once delving into it concerning PostgreSQL, I
must admit my motives not deep enough in the end for a such challenge,
still I believe in other case e.g. a collection of recommended links and
notes already in your hands might give the critical push to somebody.

After all, I looks like an RDBMS like PostgreSQL, in contrast to 'ordinary'
OO systems, much better matches Mercury, with
* Hindley-Milner mapping much easier to the relational representation,
* the known relationship between logic programming and relational algebra,
* somewhat similar requirements in regard of purity.

As far as I remember, my inquiries led to the outcome that GC harmonizing
should be the major issue of such an effort – so a such little collection
of info already present in future might help in estimating, and lowering,
the expenditure of a such project early.

Others just might enjoy studying it.

Cheers, and great esteem for the work, Nick


2015-01-20 2:00 GMT+01:00 Julien Fischer <jfischer at opturion.com>:

>
> Hi Paul,
>
> I've finally had a change to look at this some more.
>
> On Sat, 15 Nov 2014, Paul Bone wrote:
>
>  If anyone would like to test this on Windows that would be helpful.  In
>> particular I'm not sure how the symlink from boehm_gc/libatomic_ops to
>> libatomic_ops will be handled on a windows file system.
>>
>
> On MSYS it results in an error, you will need to copy the libatomic_ops
> directory on Windows.   It's probably alright on Cygwin, so if the
> output of uname matches "*MINGW*" you should copy instead of link.
>
> One other problem I have noticed with the upgraded collector is that if
> your compiler and related tools are installed in C:\Program Files\...
> then various automake / libtool generated things don't handle spaces in
> directory paths correctly and the whole thing breaks.  (For MinGW64, the
> issue seems to be related to the fact that the value of LD is directory
> qualified -- and not suitably escaped -- in libatomic_ops/Makefile.
> Unfortunately, I haven't yet managed to work out what is actually
> filling this value in.)  I'll retry MinGW64 with the development tools
> installed in a directory without spaces.
>
> Cheers,
> Julien.
>
> _______________________________________________
> developers mailing list
> developers at lists.mercurylang.org
> https://www.mercurylang.org/lists/listinfo/developers
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurylang.org/archives/developers/attachments/20150120/c4c6ed06/attachment.html>


More information about the developers mailing list