Skip to content

gchunt is a tool to identify and keep in check GC usage of D projects.

License

Notifications You must be signed in to change notification settings

DmitryOlshansky/gchunt

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

38 Commits
 
 
 
 
 
 
 
 
 
 

Repository files navigation

gchunt

gchunt is a tool is to help D developers identify and keep in check usage of GC in their projects.

How it works

gchunt transforms a stream of GC usage warnings of a D compiler to a nice wiki table. This relies on 2.066 D frontend feature to print GC allocation points.

For a given project build log, a wiki-table is generated, with columns containing:

  • module name
  • artifact name (as in someClass.someMethod.innerFunction)
  • set of source-links to the exact lines of that specific revision
  • reasons for GC allocation
  • a place for user comments (solutions)

Currently source-links are generated to github source browser, but it's readily hackable to support any other code hosting.

See wiki page for example output.

# Add `-vgc` flag to your build command
# Example for rdmd:
rdmd --build-only -vgc mymain.d > out.vgc

# you might want to check that it does contain 
# lines with vgc messages (i.e. the flag was properly set)
grep -c vgc out.vgc # count all 'vgc' words

# Then run gchunt on compiler's log
<path-to>/gchunt < out.vgc > report.wiki

# report.wiki contains table copy-pastable to any Wiki enigne
# with MediaWiki syntax support (e.g. GitHub)

Advanced usage

Reloading comments from wiki

If gchunt finds talk.gchunt file in the current directory, it assumes this file contains wiki table with user comments from some previous run. Comments are parsed from this wiki dump and attached (these that can be matched) to the same artifacts in this run. This allows iterative work on a GC usage of a project in parallel with its development.

Blacklisting

If gchunt finds blacklist.gchunt file in the current directory it's used to blacklist output of various artifacts. The file format is plain text of <module-name>:<pattern> on each line.

Pattern matching follows simple convention that * is anything that doesn't look like the next character in the pattern. For these comfortable with regex, it means: a*d* is quivalent to the regex pattern a[^d]*d.*.

Example for phobos:

std.typecons:MemberFunctionGenerator.*
std.internal.digest.sha_SSSE3:*
std.typecons:Tuple.injectNamedFields

Which blacklists all output for std.internal.digest.sha_SSE3 (a CTFE-heavy module), specifically singles out Tuple.injectNamedFields in std.typecons and everything that starts with MemberFunctionGenerator..

Building

gchunt uses D's de-facto standard dub build tool (and package manager).

Once dub is installed, the build is as simple as:

# if all goes well should produce 'gchunt', a standalone binary
dub build -b plain

Installation is simply copying it to some directory in your PATH.

About

gchunt is a tool to identify and keep in check GC usage of D projects.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages