Comparing changes
Open a pull request
base repository: m-labs/flickernoise
base: 96baf34
head repository: m-labs/flickernoise
compare: 1c031ff
- 13 commits
- 13 files changed
- 1 contributor
Commits on Dec 29, 2011
-
-
parser.y: plug various memory leaks in the parser
lemon auto-frees only tokens and nodes that are not referenced in the rule's action. Since most of these are malloc'ed containers from which we only use some of the content, we need to explicitly free them.
-
compiler/: only get unique tokens for things looking like identifiers
This patch removes the special-casing of tokens beginning with non-alphanumeric characters and teaches fpvm_parse which tokens should be treated like identifiers.
-
ptest.c: new option -n runs for repeated execution; extended usage
-n runs is for profiling and easier memory leak hunting. ptest now also detects that -c and -f conflict.
-
ptest/Makefile: access FPVM includes via MMDIR, not RTEMS_MAKEFILE_PATH
Sanity, at last ! :-)
-
compiler.c: free unique names only after we're done with them
This left a small but non-growing memory leak.
-
-
merge compiler/fpvm.c into compiler/compiler.o and stop using fpvm_* …
…prefix We don't need the fpvm.c "bridge" anymore. Also, since these elements are no longer in libfpvm, the old names would be confusing.
-
compiler: file2h -c passes input through cpp -P; use this to shrink i…
…nfra-fnp.h This removes comments and redundant whitespace at build time, speeding up run-time parsing.
-
compiler/test/patches: enable memory leak checking when using valgrind
To do: we should always check for memory leaks with valgrind. However, there are still a few left in error handling that would trip the test.
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 96baf34...1c031ff