Draft
Conversation
Pure copy of callgrind/ to tracegrind/ with symbol prefix rename CLG_ → TG_ (expanding to vgTracegrind_), header guards updated, public header renamed to tracegrind.h with TRACEGRIND_* macros. No behavioral changes — output is still identical to callgrind. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Replace callgrind's accumulated callgraph output with streaming CSV trace data emitted at function ENTER/EXIT boundaries. Each row contains delta counters since the last sample, enabling per-call cost attribution. Key changes: - dump.c: Replace callgraph output with CSV trace (trace_open/emit/close) - callstack.c: Hook push/pop_call_stack to emit ENTER/EXIT samples - threads.c: Add per-thread last_sample_cost for delta tracking - global.h: Add trace_output struct and per-thread sample state - main.c: Open trace at init, close at fini, update copyright Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Add --output-format=csv|msgpack option. MsgPack format uses LZ4 block compression achieving ~12x compression vs CSV. New files: - tg_msgpack.c/h: MsgPack encoder (write-only) - tg_lz4.c/h: LZ4 compression wrapper with VG_() adaptations - lz4.c/h: Vendored LZ4 library (BSD-2-Clause) - docs/tracegrind-msgpack-format.md: Format specification Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
- Update msgpack format to version 2 with event_schemas - Each event type (ENTER, EXIT, FORK) has its own column schema - FORK events use minimal 4-element format: [seq, tid, event, child_pid] - Remove CSV output format entirely (msgpack-only now) - Add decode-trace.py script for debugging trace files - Add fork detection via post-syscall handler for fork/clone/vfork Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
art049
force-pushed
the
tracegrind-tool
branch
from
4ccc4f9 to
864a751
Compare
Add tracegrind configurations to the benchmark suite: - tracegrind/default: basic tracing - tracegrind/cache-sim: with cache simulation - tracegrind/cache-sim+systime: with cache sim and syscall timing This allows direct performance comparison between callgrind and tracegrind. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Detect available tools at startup and only run benchmarks for tools that are present. This fixes CI failures when running against upstream valgrind which doesn't have tracegrind. Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.