This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

Compile & Link Time Depends On Compiler Installation Location



Hello,

I want to install the compiler separately from CCS so that we can control the compiler version independently of the CCS version.

I installed CCS12.4 (with 2.1.3.LTS) and separately installed 2.1.2.LTS as follows:

However, I noticed a gross difference in the project build time:

    2.1.3.LTS : 33s

    2.1.2.LTS : 1m 4s

The "standalone" compiler takes almost double the time.

Why is there such a difference in the build time please? I doubt it is to do with the compiler version but have an open mind.

  • The "standalone" compiler takes almost double the time.

    I don't think the fact that it is "standalone" is what is making the difference. Can you also try the standalone 2.1.2 compiler and see what happens?

  • Can you also try the standalone 2.1.2 compiler

    Do you mean standalone 2.1.3? The standalone version is already 2.1.2.

    I have 2.1.3 standlone installed but CCS won't discover it. I guess it can't cope with two or more compilers of the same version.

    I also installed the latest and greatest 3.2.0.LTS. Here's the latest results with the latest project code:

    1) TI Clang v3.2.0.LTS c:\ti\ti-cgt-armllvm_3.2.0.LTS                                                   1m 23s     
    2) TI Clang v2.1.3.LTS C:\ti\ccs1240\ccs\tools\compiler\ti-cgt-armllvm_2.1.3.LTS      33s
    3) TI Clang v2.1.2.LTS c:\ti\ti-cgt-armllvm_2.1.2.LTS                                                   34s

    So ti seems the problem has shifted from one standalone compiler to another.

    What I also noticed was when using compilers (2) and (3), it uses max CPU load on my PC. When I use compiler (1), the CPU load doesn't go above 50%. It almost as if the number of parallel jobs is halved when using (1).

  • So ti seems the problem has shifted from one standalone compiler to another.

    Ok, this is weird. I've never heard of such an issue. I will need to see if I can reproduce this,

  • Thanks Ki but I think maybe we should close this issue. I tried the same test today and I don't get the same problem. Weird indeed but looks like it's local to my machine. Apologies for wasting your time.

  • I tried the same test today and I don't get the same problem.

    I'm wondering if it is like something that happens initially after you just installed a new compiler and using it for the first time in CCS. Maybe the project gets indexed again and the re-indexing while the build is kick off may cause the build to slow down. Subsequent builds improve because the indexing is done.

  • I think that if indexing (or something else) was consuming CPU time I would see high CPU load but when I saw the problem, the CPU was not fully utilized. I still can't replicate the problem today so I guess we can drop it until or if it reappears.