Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: reindent comment
Date: Wed, 28 Jan 2004 05:57:00 -0000	[thread overview]
Message-ID: <vt2llns4nv1.fsf@zenia.home> (raw)


Committed as obvious.

2004-01-27  Jim Blandy  <jimb@redhat.com>

	* dwarf2read.c (read_func_scope): Re-indent comment.

Index: gdb/dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.128
diff -c -r1.128 dwarf2read.c
*** gdb/dwarf2read.c	28 Jan 2004 04:02:51 -0000	1.128
--- gdb/dwarf2read.c	28 Jan 2004 04:04:04 -0000
***************
*** 2173,2199 ****
      {
        struct die_info *spec_die = die_specification (die, cu);
  
! 	  /* NOTE: carlton/2004-01-23: We have to be careful in the
! 	     presence of DW_AT_specification.  For example, with GCC
! 	     3.4, given the code
  
!                namespace N {
! 	         void foo() {
! 		   // Definition of N::foo.
! 	         }
! 	       }
  
! 	     then we'll have a tree of DIEs like this:
  
! 	     1: DW_TAG_compile_unit
!                2: DW_TAG_namespace        // N
!                  3: DW_TAG_subprogram     // declaration of N::foo
!                4: DW_TAG_subprogram       // definition of N::foo
!                     DW_AT_specification   // refers to die #3
  
!              Thus, when processing die #4, we have to pretend that
!              we're in the context of its DW_AT_specification, namely
!              the contex of die #3.  */
  	
        if (spec_die != NULL)
  	{
--- 2173,2199 ----
      {
        struct die_info *spec_die = die_specification (die, cu);
  
!       /* NOTE: carlton/2004-01-23: We have to be careful in the
!          presence of DW_AT_specification.  For example, with GCC 3.4,
!          given the code
  
!            namespace N {
!              void foo() {
!                // Definition of N::foo.
!              }
!            }
  
!          then we'll have a tree of DIEs like this:
  
!          1: DW_TAG_compile_unit
!            2: DW_TAG_namespace        // N
!              3: DW_TAG_subprogram     // declaration of N::foo
!            4: DW_TAG_subprogram       // definition of N::foo
!                 DW_AT_specification   // refers to die #3
  
!          Thus, when processing die #4, we have to pretend that we're
!          in the context of its DW_AT_specification, namely the contex
!          of die #3.  */
  	
        if (spec_die != NULL)
  	{


                 reply	other threads:[~2004-01-28  5:57 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vt2llns4nv1.fsf@zenia.home \
    --to=jimb@redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox