This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[PATCH] Fix NOTE_INSN_* list in rtl.texi


The NOTE_INSN_* list in the rtl.texi refers to three constants that 
are no longer in insn-notes.def (SETJMP, LOOP_VTOP, LOOP_CONT). There 
are some constants that are not documented, however.

I'd be grateful for a more descriptive text for 
NOTE_INSN_{VAR_LOCATION,EXPECTED_VALUE,BASIC_BLOCK} :) Others are 
just shamelessly copied from insn-notes.def.

2004-12-01  Alexey Neyman  <alex.neyman@auriga.ru>

	* doc/rtl.texi: Sync up the NOTE_INSN_* list with
	insn-notes.def.

-- 
Don't be afraid of love.
Are you afraid of love?
                        -- Pkunks, SC2
*** /home/avn/tmp/gcc.orig/gcc/doc/rtl.texi	2004-11-24 10:58:45.000000000 +0300
--- /home/avn/tmp/gcc.setjmp/gcc/doc/rtl.texi	2004-12-01 14:40:33.909448584 +0300
***************
*** 3056,3070 ****
  of a level of scoping of variable names.  They control the output
  of debugging information.
  
- @findex NOTE_INSN_EH_REGION_BEG
- @findex NOTE_INSN_EH_REGION_END
- @item NOTE_INSN_EH_REGION_BEG
- @itemx NOTE_INSN_EH_REGION_END
- These types of notes indicate the position of the beginning and end of a
- level of scoping for exception handling.  @code{NOTE_BLOCK_NUMBER}
- identifies which @code{CODE_LABEL} or @code{note} of type
- @code{NOTE_INSN_DELETED_LABEL} is associated with the given region.
- 
  @findex NOTE_INSN_LOOP_BEG
  @findex NOTE_INSN_LOOP_END
  @item NOTE_INSN_LOOP_BEG
--- 3056,3061 ----
***************
*** 3073,3089 ****
  of a @code{while} or @code{for} loop.  They enable the loop optimizer
  to find loops quickly.
  
- @findex NOTE_INSN_LOOP_CONT
- @item NOTE_INSN_LOOP_CONT
- Appears at the place in a loop that @code{continue} statements jump to.
- 
- @findex NOTE_INSN_LOOP_VTOP
- @item NOTE_INSN_LOOP_VTOP
- This note indicates the place in a loop where the exit test begins for
- those loops in which the exit test has been duplicated.  This position
- becomes another virtual start of the loop when considering loop
- invariants.
- 
  @findex NOTE_INSN_FUNCTION_BEG
  @item NOTE_INSN_FUNCTION_END
  Appears at the start of the function body, after the function
--- 3064,3069 ----
***************
*** 3096,3104 ****
  does not suffice for returning).  This note may be deleted by jump
  optimization.
  
! @findex NOTE_INSN_SETJMP
! @item NOTE_INSN_SETJMP
! Appears following each call to @code{setjmp} or a related function.
  @end table
  
  These codes are printed symbolically when they appear in debugging dumps.
--- 3076,3120 ----
  does not suffice for returning).  This note may be deleted by jump
  optimization.
  
! @findex NOTE_INSN_PROLOGUE_END
! @findex NOTE_INSN_EPILOGUE_BEG
! @item NOTE_INSN_PROLOGUE_END
! @itemx NOTE_INSN_EPILOGUE_BEG
! These notes appear right after the function prologue and right before
! the function epilogue, respectively.
! 
! @findex NOTE_INSN_EH_REGION_BEG
! @findex NOTE_INSN_EH_REGION_END
! @item NOTE_INSN_EH_REGION_BEG
! @itemx NOTE_INSN_EH_REGION_END
! These types of notes indicate the position of the beginning and end of a
! level of scoping for exception handling.  @code{NOTE_BLOCK_NUMBER}
! identifies which @code{CODE_LABEL} or @code{note} of type
! @code{NOTE_INSN_DELETED_LABEL} is associated with the given region.
! 
! @findex NOTE_INSN_REPEATED_LINE_NUMBER
! @item NOTE_INSN_REPEATED_LINE_NUMBER
! These types of notes are generated whenever a duplicate line number note
! is output. For example, one is output after the end of an inline function,
! in order to prevent the line containing the inline call from being counted
! twice in gcov.
! 
! @findex NOTE_INSN_VAR_LOCATION
! @item NOTE_INSN_VAR_LOCATION
! FIXME!
! 
! @findex NOTE_INSN_EXPECTED_VALUE
! @item NOTE_INSN_EXPECTED_VALUE
! FIXME!
! 
! @findex NOTE_INSN_BASIC_BLOCK
! @item NOTE_INSN_BASIC_BLOCK
! FIXME!
! 
! @findex NOTE_INSN_UNLIKELY_EXECUTED_CODE
! @item NOTE_INSN_UNLIKELY_EXECUTED_CODE
! These notes record that the current basic block is unlikely to be executed and
! should be moved to the UNLIKELY_EXECUTED_TEXT_SECTION.
  @end table
  
  These codes are printed symbolically when they appear in debugging dumps.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]