Bug 694 - compilation of src/simulator/time.cc with gcc eats up to 1.4G of RAM
compilation of src/simulator/time.cc with gcc eats up to 1.4G of RAM
Status: RESOLVED FIXED
Product: ns-3
Classification: Unclassified
Component: core
ns-3-dev
All All
: P3 critical
Assigned To: ns-bugs
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-09-29 14:12 UTC by Andrey Mazo
Modified: 2009-11-23 09:45 UTC (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrey Mazo 2009-09-29 14:12:02 UTC
Steps to reproduce:
1) hg up -r 1a805e0bf415
2) ./waf configure -d optimized --enable-static
3) ./waf build

Compilation of time.cc eats up to 1.4G of RAM and about 5 minutes with gcc-4.3.2 and gcc-4.4.1 (not tested on other compilers yet).
This makes the whole compilation of ns-3 nearly impossible on low-memory machines.

gcc-4.1.2 produces a bunch of warnings:
../src/simulator/time.cc: In member function 'virtual bool ns3::ConversionTestCase::DoRun()':
../src/simulator/time.cc:629: warning: passing 'double' for argument 1 to 'ns3::Time ns3::MilliSeconds(uint64_t)'
../src/simulator/time.cc:629: warning: passing 'double' for argument 1 to 'ns3::Time ns3::MicroSeconds(uint64_t)'
../src/simulator/time.cc:629: warning: passing 'double' for argument 1 to 'ns3::Time ns3::NanoSeconds(uint64_t)'
../src/simulator/time.cc:629: warning: passing 'double' for argument 1 to 'ns3::Time ns3::PicoSeconds(uint64_t)'
Comment 1 Andrey Mazo 2009-10-06 14:22:56 UTC
(In reply to comment #0)
> Compilation of time.cc eats up to 1.4G of RAM and about 5 minutes with
> gcc-4.3.2 and gcc-4.4.1 (not tested on other compilers yet).
> This makes the whole compilation of ns-3 nearly impossible on low-memory
> machines.
changeset d0b9a6e08e47 workarounds this problem.