Activity
From 03/19/2014 to 04/17/2014
04/09/2014
- 03:31 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> You can check in and distribute the update.
Committed to bzr rev 10507.
04/08/2014
- 03:32 PM Feature #2251: improve the call graph generation
- You can check in and distribute the update.
- 02:42 PM Feature #2251: improve the call graph generation
- This fixes the incompatibility when running the callgraph on a machine with different case-sensitivity than the one f...
04/03/2014
- 05:49 AM Feature #2251: improve the call graph generation
- The branch rev 10504 contains the fix for generating the callgraph reports on windows (the filename should have been ...
03/26/2014
- 03:49 PM Feature #2251 (Closed): improve the call graph generation
- 02:23 PM Feature #2251 (Review): improve the call graph generation
- 02:23 PM Feature #2251: improve the call graph generation
- Branch revision 10518 was committed to the 10496/10497, both on trunk master on devsrv01 and filesrv01.
03/25/2014
- 04:15 PM Feature #2251: improve the call graph generation
- > Regarding note 97: I think bzr merge should do the trick, to merge the branch into the trunk
Yes, that was my pl... - 02:12 PM Feature #2251: improve the call graph generation
- The update passed runtime and conversion testing (both server and MAJIC code).
Regarding note 97: I think @bzr mer... - 03:49 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> > BTW, to "release" a branch to the trunk, is there another way beside just copying the branch co...
03/24/2014
- 03:26 PM Feature #2251: improve the call graph generation
- > BTW, to "release" a branch to the trunk, is there another way beside just copying the branch content (without the ....
- 02:21 PM Feature #2251: improve the call graph generation
- See the branch 10517 revision (which was rebased) for the latest changes (some doc changes and a minor fix). This is ...
- 06:44 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> 1. What is your general sense about the performance? Do you feel it is "good", "bad" or somethin...
03/21/2014
- 01:27 PM Feature #2251: improve the call graph generation
- I saw your note about the performance metrics in #2260. The numbers seem pretty good for processing such a large pro...
- 01:24 PM Feature #2251: improve the call graph generation
- Code Review branch rev 10514
I am good with the changes. If you still think it is finished, go ahead with regress... - 12:40 PM Feature #2251: improve the call graph generation
- Branch rev 10514 adds the "-u" argument for CallGraphGenerator, which uses the passed filename list and all ambiguous...
- 10:17 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> One question: it looks to me like each call-graph run is fresh and we don't support incremental c... - 09:20 AM Feature #2251: improve the call graph generation
- Code Review branch rev 10513
Everything looks good.
One question: it looks to me like each call-graph run is fr... - 08:44 AM Feature #2251: improve the call graph generation
- > I think I'm missing some index configuration, as CallGraphWorker.findNodeById doesn't look like it uses an index (i...
- 08:40 AM Feature #2251: improve the call graph generation
- Code Review branch rev 10512
Everything looks good, except that the ProgressPatternWorker change is not needed. @...
03/20/2014
- 05:04 PM Feature #2251: improve the call graph generation
- Branch rev 10512 contains:
- the fix for the FILE-NAME preproc var
- some misc fixes
- some performance improvemen... - 09:30 AM Feature #2251: improve the call graph generation
- OK, thanks for clarifying this.
- 09:02 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> path/to/first/filename.p
> path/to/second/filename.p
> other/path/filename.p
>
> A reverse s... - 08:56 AM Feature #2251: improve the call graph generation
- My concern is that this algorithm can match multiple filenames in the project, making the results ambiguous.
Assum... - 08:25 AM Feature #2251: improve the call graph generation
- Greg Shah wrote:
> 2. I'm a little worried that the @CallGraphWorker.resolveExternalPrograms()@ approach of using th... - 11:32 AM Feature #1519: report improvements
- A report listing hard coded absolute filenames would be useful.
- 11:32 AM Feature #1519: report improvements
- Dynamic extent and extent parameter reports are already done (they were done before now).
The incompatible program... - 08:53 AM Feature #1512 (Closed): separate match processing into a single pass of all report filters per file
- 08:50 AM Feature #1520: design gap analysis approach
- We want to make the marking as data driven as possible. This will allow rapid enhancement of the facilities without ...
03/19/2014
- 05:11 PM Feature #2251: improve the call graph generation
- Code Review branch rev 10510
1. Please add a comment into the init-rules of post_parse_fixups.xml explaining that ... - 02:36 PM Feature #2251: improve the call graph generation
- Rev 10510 contains:
* fix for the @RUN <internal-proc>@ reported as missing external procedures.
* fix for @RUN por... - 02:16 PM Feature #2251: improve the call graph generation
- There is a way to get rid of the non-indexed suffix search, when looking for external programs: keep, alongside the @...
- 12:26 PM Bug #2262: ON statement preprocessing and parsing issues related to unmatched quotes or tilde
- This testcase (checked in as on_stmt_event_as_single_or_double_quote.p) shows the issues:...
- 11:13 AM Bug #2262 (New): ON statement preprocessing and parsing issues related to unmatched quotes or tilde
Also available in: Atom