Permalink
Browse files

PDD13: The debug segment has no line numbers

The debug segment consists only of a list of offset to filename
mappings.  While a long table of opcodes to line numbers might be
useful, it doesn't exist.  So remove the pretty description of it.
  • Loading branch information...
1 parent 5a43b68 commit 66923d2f091f10d32edf1d807e49ccc44c5ca364 @Benabik Benabik committed Jun 26, 2012
Showing with 5 additions and 27 deletions.
  1. +5 −27 docs/pdds/draft/pdd13_bytecode.pod
@@ -458,34 +458,12 @@ following form.
=head4 PIR Debug Segment
-This segment stores the filenames and line numbers of PIR code that was
-compiled to bytecode. The segment comes in two parts.
+This segment stores a list of mappings between offsets in the bytecode and
+filenames, indicating that the bytecode from that point on until the next
+entry was generated from the PIR found in the given filename
-=over 4
-
-=item A list of mappings between instructions in the bytecode and line
-numbers, with one entry per instruction
-
-=item A list of mappings between offsets in the bytecode and filenames,
-indicating that the bytecode from that point on until the next entry was
-generated from the PIR found in the given filename
-
-=back
-
-The length of the table of line number mappings is given by the last field
-of the segment header.
-
-Then comes the table:
-
- +--------+--------+--------------------------------------------------------+
- | Offset | Length | Description |
- +--------+--------+--------------------------------------------------------+
- | 0 | 1 | Line number for the offset in the bytecode. |
- +--------+--------+--------------------------------------------------------+
-
-Then comes an opcode with n, the number of file mappings.
-
-Then come n mappings.
+The segment begins with an opcode with n, the number of file mappings. Then
+come n mappings:
+--------+--------+--------------------------------------------------------+
| Offset | Length | Description |

0 comments on commit 66923d2

Please sign in to comment.