summaryrefslogtreecommitdiff
path: root/README.markdown
diff options
context:
space:
mode:
authorJosé Fonseca <jose.r.fonseca@gmail.com>2012-11-14 07:21:01 +0000
committerJosé Fonseca <jose.r.fonseca@gmail.com>2012-11-14 07:21:49 +0000
commitbce31f64b76d8aa9a933f0f6a1a2d6ff95b63f33 (patch)
tree9384647b65432493628a296c937162f7e6695f46 /README.markdown
parent65788a69cd34e015823ca6532852b4168e291c75 (diff)
Update use/mention of options.
Diffstat (limited to 'README.markdown')
-rw-r--r--README.markdown10
1 files changed, 5 insertions, 5 deletions
diff --git a/README.markdown b/README.markdown
index ab145305..af54b7f9 100644
--- a/README.markdown
+++ b/README.markdown
@@ -51,7 +51,7 @@ Replay an OpenGL trace with
glretrace application.trace
-Pass the `-sb` option to use a single buffered visual. Pass `--help` to
+Pass the `--sb` option to use a single buffered visual. Pass `--help` to
`glretrace` for more options.
EGL traces must be replayed with `eglretrace` instead of `glretrace`.
@@ -341,11 +341,11 @@ Profiling a trace
You can perform gpu and cpu profiling with the command line options:
- * `-pgpu` record gpu times for frames and draw calls.
+ * `--pgpu` record gpu times for frames and draw calls.
- * `-pcpu` record cpu times for frames and draw calls.
+ * `--pcpu` record cpu times for frames and draw calls.
- * `-ppd` record pixels drawn for each draw call.
+ * `--ppd` record pixels drawn for each draw call.
The results from this can then be read by hand or analysed with a script.
@@ -354,7 +354,7 @@ table which displays profiling results per shader.
For example, to record all profiling data and utilise the per shader script:
- ./glretrace -pgpu -pcpu -ppd foo.trace | ./scripts/profileshader.py
+ ./glretrace --pgpu --pcpu --ppd foo.trace | ./scripts/profileshader.py
Advanced usage for OpenGL implementors