Re: c++/6387

Re: c++/6387

[Wolfgang Bangerth]

The following reply was made to PR debug/6387; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/6387
Date: Sat, 14 Dec 2002 13:30:50 -0600 (CST)

 Just for the record: this patch (which was commited at the same time)
   diff -r1.12379 -r1.12380
   0a1,11
   > 2001-12-18  Jakub Jelinek  <jakub@redhat.com>
   >
   >       * config/linux.h (PREFERRED_DEBUGGING_TYPE): Remove. 
   >       * config/sparc/linux.h (PREFERRED_DEBUGGING_TYPE): Remove.
   >       * config/sparc/linux64.h (PREFERRED_DEBUGGING_TYPE): Remove.
   >       (CC1_SPEC): Don't default to -gstabs+ if -m32.
   >
   > 2001-12-05  David O'Brien  <obrien@FreeBSD.org>
   >
   >       * elfos.h (PREFERRED_DEBUGGING_TYPE): Change to DWARF2_DEBUG.
 
 is where high priority regression PR 6387 started, which has this 
 testcase:
 -----------------------
 void foo();
 void bar() {
   struct A { A() { foo(); } } a;
 }
 -----------------------
 and yields the following result with -g1 -fPIC:
 
 bash-2.05$ ../bin/gcc-2001-12-25/bin/c++ -fPIC -g1 -c PR6387.cc
   PR6387.cc:5: Internal compiler error in dwarf2out_finish, at 
   dwarf2out.c:11959
 
 Given the log message, it might well be that the problem originated 
 earlier and a change in meaning of -g1 now exposed the problem. Maybe the 
 authors of the patch can comment on how the new meaning of -g1 can be 
 reproduced with compilers that preceded this patch?
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 
 

Re: c++/6387

[Wolfgang Bangerth]

The following reply was made to PR debug/6387; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/6387
Date: Sat, 14 Dec 2002 13:52:21 -0600 (CST)

 > How about `-gdwaf -g1'?
 
 Close. The switch was to dwarf2. -gdwarf -g1 works before and after that 
 change, -gdwarf-2 -g1 does not work before or after the change. So I'll at 
 this to flags and run it again. (Sorry for not noticing it before, I tried 
 -gdwarf-2 alone, but did not realize that it is necessary to use -g1 as 
 well...)
 
 With -gdwarf-2 -g1, the failure appeared before 2001-01-01, which 
 presently the limit of the compilers I have on my disk, so I won't be able 
 to check this further.
 
 Regards
   Wolfgang
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth