[llvm-dev] Issues with Eclipse CDT4
Joachim Durchholz via llvm-dev
llvm-dev at lists.llvm.org
Sun Oct 11 15:15:33 PDT 2015
Am 10.10.2015 um 21:14 schrieb Tim Northover:
> On 10 October 2015 at 04:16, Joachim Durchholz via llvm-dev
> <llvm-dev at lists.llvm.org> wrote:
>> is this the right place to discuss getting LLVM built using Eclipse,
>> as described on http://llvm.org/docs/GettingStarted.html?
> It's probably as good as anywhere,
> but I don't think there's much
> that's different from a regular build. As far as I'm aware you just
> tell CMake to generate an Eclipse project and hope you've got enough
> memory to load it.
32 GB should be enough for everyone ;-)
... oh darnit. Right. I forgot that Eclipse comes configured to use just
512 MB and needs to be reconfigured for more.
I just finished a test run with an allowance of 16 GB. The biggest
pre-GC memory usage was 6.9 G, the biggest post-GC usage 6.9 GB.
From this I come to the following recommendations:
- 2 GB as the absolute minimum,
- 3 GB "likely workable", and
- 7 GB optimum.
> I don't really use Eclipse, but it seemed to work OK here after I'd
> removed tools/clang/INPUTS/macro_pounder_fn.c (there's probably a way
> to tell Eclipse not to bother indexing that file, but I don't know
> What problem are you seeing?
It ran straight into GC thrashing, that's what happened - with enough
memory, it took a mere 20 minutes (Core i7 with an SSD, YMMV).
Now I'm hitting exceptions when reopening the project in Eclipse, and
stopping the indexer, which bad though I don't know how bad.
It's on Eclipse Mars, so if Luna does not have this problem, don't
upgrade your Eclipse yet!
I'll go and take this to the CDT bug tracker.
More information about the llvm-dev