| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0000031 | mercury | Bug | public | 2007-12-09 03:36 | 2007-12-10 18:00 | ||||
| Reporter | ony | ||||||||
| Assigned To | juliensf | ||||||||
| Priority | normal | Severity | minor | Reproducibility | always | ||||
| Status | resolved | Resolution | won't fix | ||||||
| Product Version | |||||||||
| Target Version | Fixed in Version | ||||||||
| Summary | 0000031: modules compilation on 64-bit platform eats too much memory | ||||||||
| Description | During 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 Information | CPU: 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) | ||||||||
| Tags | No tags attached. | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
juliensf (administrator) 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 |
|
ony (reporter) 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. |
|
juliensf (administrator) 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. |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2007-12-09 03:36 | ony | New Issue | |
| 2007-12-09 03:42 | juliensf | Note Added: 0000062 | |
| 2007-12-09 03:42 | juliensf | Status | new => feedback |
| 2007-12-09 04:16 | ony | File Added: build.log.bz2 | |
| 2007-12-09 04:16 | ony | File Added: emerge_start.log.bz2 | |
| 2007-12-09 04:16 | ony | File Added: environment.bz2 | |
| 2007-12-09 04:22 | ony | Note Added: 0000064 | |
| 2007-12-09 04:22 | ony | File Added: config.log.bz2 | |
| 2007-12-10 18:00 | juliensf | Status | feedback => resolved |
| 2007-12-10 18:00 | juliensf | Resolution | open => won't fix |
| 2007-12-10 18:00 | juliensf | Assigned To | => juliensf |
| 2007-12-10 18:00 | juliensf | Note Added: 0000065 | |
| Issue History |