Mercury Bugs - mercury
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0000031mercuryBugpublic2007-12-09 03:362007-12-10 18:00
Reporterony 
Assigned Tojuliensf 
PrioritynormalSeverityminorReproducibilityalways
StatusresolvedResolutionwon't fix 
PlatformOSOS Version
Product Version 
Target VersionFixed in Version 
Summary0000031: modules compilation on 64-bit platform eats too much memory
DescriptionDuring building process of v0.13.1 on amd64-compatible platform there is stage with building modules (Internals) and at that moment there is huge memory usage which finally produce out of memory (tried at 2 GB ram + 4 GB swap).
As contrary to that 32-bit version is built normally on the same platform.
Additional InformationCPU: Intel Core 2 Duo E6600
RAM: 2 GB
OS: GNU/Linux 2.6.23-gentoo-r2 0000002 SMP
Distribution: Gentoo Linux amd64 (default-linux/amd64/2007.0 profile)
GCC: gcc version 4.2.2 (Gentoo 4.2.2 p1.0)
TagsNo tags attached.
Relationships
Attached Filesbz2 build.log.bz2 (16,040) 2007-12-09 04:16
https://bugs.mercurylang.org/file_download.php?file_id=25&type=bug
bz2 emerge_start.log.bz2 (818) 2007-12-09 04:16
https://bugs.mercurylang.org/file_download.php?file_id=26&type=bug
bz2 environment.bz2 (21,463) 2007-12-09 04:16
https://bugs.mercurylang.org/file_download.php?file_id=27&type=bug
bz2 config.log.bz2 (17,395) 2007-12-09 04:22
https://bugs.mercurylang.org/file_download.php?file_id=28&type=bug

Notes
(0000062)
juliensf   
2007-12-09 03:42   
Hi,

What does building modules (Internals) mean?
Do you mean when the file compiler/modules.m is being compiled?

At what stage of compilation is this happening? When Mercury is being compiled
to C code, or when the C code is being compiled to object code.

It would be helpful if you could provide a copy of the output of the build process
(0000064)
ony   
2007-12-09 04:22   
Sorry, I'm newbie in Mercury just starting to use, but looks like it have problems during building modules in library subdirectory using "mmc".

You can find building process log in attachment build.log.bz2.
At this time I've limited memory usage to 1.5 GB to avoid breaking of other processes. Please see emerge_start.log.bz2 for info.
config.log.bz2 - is copied and compressed from topdir.
(0000065)
juliensf   
2007-12-10 18:00   
The entire configuration process looks very odd for that type of machine.
My guess is that it is something to do with the way the Gentoo package is running the
build process.

I think this should be reported as a bug in the Gentoo Mercury package, via bugs.gentoo.org.

Issue History
Date ModifiedUsernameFieldChange
2007-12-09 03:36onyNew Issue
2007-12-09 03:42juliensfNote Added: 0000062
2007-12-09 03:42juliensfStatusnew => feedback
2007-12-09 04:16onyFile Added: build.log.bz2
2007-12-09 04:16onyFile Added: emerge_start.log.bz2
2007-12-09 04:16onyFile Added: environment.bz2
2007-12-09 04:22onyNote Added: 0000064
2007-12-09 04:22onyFile Added: config.log.bz2
2007-12-10 18:00juliensfStatusfeedback => resolved
2007-12-10 18:00juliensfResolutionopen => won't fix
2007-12-10 18:00juliensfAssigned To => juliensf
2007-12-10 18:00juliensfNote Added: 0000065