From f5e1ea819b77fca763d293434a3f22ecdb136ec8 Mon Sep 17 00:00:00 2001 From: rgrjr Date: Mon, 4 Feb 2008 03:03:56 +0000 Subject: [PATCH] + --debug is now --imcc-debug; make this more consistent with -D. + Remove references to "IMCC" as a program. + Add "-V" para. + Explain that "Generated files" applies to JIT debugging. git-svn-id: https://svn.perl.org/parrot/trunk@25485 d31e2699-5ff4-0310-a27c-f18f2fbe73fe --- docs/running.pod | 33 +++++++++++++-------------------- 1 file changed, 13 insertions(+), 20 deletions(-) diff --git a/docs/running.pod b/docs/running.pod index 08e5f255a3..f0a9938ce5 100644 --- a/docs/running.pod +++ b/docs/running.pod @@ -46,29 +46,17 @@ Assume PASM input on stdin. Assume PBC file on stdin, run it. -=item -d, --debug [hexbits] +=item -d, --imcc-debug [hexbits] The B<-d> switch takes an optional argument which is considered to hold a hex value of debug bits. Without a value, debug is set to 1. -The individual bits are: +The individual bits can be listed on the command line by use of the +B<--help-debug> switch. - DEBUG_PARROT 0001 - DEBUG_LEXER 0002 - DEBUG_PARSER 0004 - DEBUG_IMC 0008 - DEBUG_CFG 0010 - DEBUG_OPT1 0020 - DEBUG_OPT2 0040 - DEBUG_PBC 1000 - DEBUG_PBC_CONST 2000 - DEBUG_PBC_FIXUP 4000 - -These can be listed on the command line by use of the B<--help-debug> switch. - -To produce really huge output on F run "imcc B<-d 0ffff> ...". Note: -if the argument is separated by whitespace from the B<-d> switch, it has to -start with a number. +To produce really huge output on F run C<"parrot B<-d 0ffff> ...">. +Note: If the argument is separated by whitespace from the B<-d> +switch, it has to start with a number. =item -h, --help @@ -100,7 +88,7 @@ disc and run. This is mainly needed for tests. One B<-v> shows which files are worked on and prints a summary over register usage and optimization stats per I. With two B<-v> switches, -IMCC prints a line per individual processing step too. +C prints a line per individual processing step too. =item -y, --yydebug @@ -108,6 +96,8 @@ Turn on yydebug in F/F. =item -V, --version +Print version information and exit. + =item -Ox Optimize @@ -246,7 +236,8 @@ assumed to know what to do with these. =head1 Generated files -If debugging is enabled these files are generated: +If JIT debugging is enabled (e.g. via C<--parrot-debug 04>), the +following additional output files are generated: file.stabs.s ... stabsfile for the program file.o ... object file with debug information @@ -254,6 +245,8 @@ If debugging is enabled these files are generated: EVAL_n.stabs.s ... stabsfile for this block EVAL_n.o ... object file with debug information +See F for further information. + =head1 About runcores The runcore (or runloop) tells Parrot how to find the C code that -- 2.11.4.GIT