User forums > Nightly builds

The 25 september 2010 build (6634) CODECOMPLETION BRANCH version is out.

<< < (9/24) > >>

Jenna:
cc debug-info: http://apt.jenslody.de/cc/cc_debug.7z

As written before, the test-project is generated from the (debian) linux-kernel sources, revision 2.6.29.
No build-options or defines, just all files from sources added to an empty project.

Loaden:

--- Quote from: jens on October 03, 2010, 11:51:36 pm ---cc debug-info: http://apt.jenslody.de/cc/cc_debug.7z

As written before, the test-project is generated from the (debian) linux-kernel sources, revision 2.6.29.
No build-options or defines, just all files from sources added to an empty project.

--- End quote ---
Thank Jens! I will look into it carefully.

Loaden:

--- Quote from: jens on October 03, 2010, 11:03:05 pm ---Another issue (not related to this), is that the symboslbrowser stays empty, if the project is opened without any shown editor.
After opening any file the symbols-browser gets filled.

--- End quote ---
Confirmed!

EDIT: It's can confirmed only Linux, and in Windows, no have this issue.
Here:

--- Quote ---bool Parser::Done()
{
    wxCriticalSectionLocker locker(s_ParserCritical);
    bool done =    m_UpFrontHeaders.IsEmpty()
                && m_SystemUpFrontHeaders.IsEmpty()
                && m_BatchParseFiles.IsEmpty()
                && m_PredefinedMacros.IsEmpty()
                && !m_NeedMarkFileAsLocal // When parsing end, this value be true always in Linux/GCC4.5.1!
                && m_PoolTask.empty()
                && m_Pool.Done();
    return done;
}
--- End quote ---

Loaden:
answer to these questions:

--- Quote from: jens on October 03, 2010, 11:03:05 pm ---Parsing takes a little more than 28 minutes, that's very long, but I get more than 1 million tokens.

--- End quote ---
1, the batch parsing time is too long:
the Linux source code you supplied contains a lot of code snippet which has grammar errors like

--- Code: ---#define AAA(x) BBB(x)
#define BBB(y) AAA(y)

#if AAA(1) && BBB(2)
void fly();
#else
void good();
#endif

--- End code ---
These code will increase the loop time(at least 100 times add compare to normal code), so the performace is bad.


--- Quote from: jens on October 03, 2010, 11:03:05 pm ---And it seems parsing is not correct, I get some strange tokens in symbol browser (see the attached picture).

--- End quote ---
2. parsing error, wrong tokens:
This was still due to the highly mixed pre-processor code, our CC only do a format match, like

"AAA BBB();" ---> BBB is a function.
"AAA BBB;"  ---> BBB is a variable.

Thus, CC is not so smart to detect and handle grammar errors. (the only method is do a "full pre-processor" before parsing)

Jenna:
This sounds reasonable.
Nevertheless, there are tokens that contain (or even begin with) whitespace, that means these tokens are invaild, so they could be (should be ?) securely removed.

Navigation

[0] Message Index

[#] Next page

[*] Previous page