From:	"Mark E." <snowball3 AT bigfoot DOT com>
To:	djgpp-workers AT delorie DOT com
Date:	Wed, 6 Dec 2000 14:54:19 -0500
MIME-Version:	1.0
Subject:	Re: DJGPP linker script update
Message-ID:	<3A2E531B.8670.20FE7F@localhost>
In-reply-to:	<200012061831.NAA25654@envy.delorie.com>
References:	<3A2E2A06 DOT 26911 DOT 52F92 AT localhost> (snowball3 AT bigfoot DOT com)
X-mailer:	Pegasus Mail for Win32 (v3.12c)
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> Do you have an idea when full dwarf2 support will be ready for users?

Just a general one.

GCC can easily be taken care of in time for gcc 3.0. However, I currently 
don't have the memory to test dwarf2 support with gcc cvs. If someone will 
test the patch below and verify it works, the tester can then either post it 
to gcc-patches or let me do it. Either way makes no difference to me. This 
will make gcc 3.0 and binutils 2.11 good to go.

I'll have to rely on someone who knows about gdb internals to please get 
dwarf2 configured in for DJGPP there once the binutils patch goes in. 

My current thinking is that we will be able to debug with dwarf2 when gcc 3.0 
is released. I can't imagine gcc 3.0 being released before a version of gdb 
with the neccessary changes to support the new abi is released. So I'd say 
when gcc 3.0 is released, dwarf2 ready versions of binutils and gdb will be 
out and so we'll be able to use dwarf2.

Here is the config change for gcc:

Index: gcc/gcc/config/i386/djgpp.h
===================================================================
RCS file: /cvs/gcc/egcs/gcc/config/i386/djgpp.h,v
retrieving revision 1.19
diff -c -p -r1.19 djgpp.h
*** djgpp.h	2000/11/02 23:29:09	1.19
--- djgpp.h	2000/12/06 19:39:36
*************** Boston, MA 02111-1307, USA.  */
*** 20,25 ****
--- 20,28 ----
  
  #include "dbxcoff.h"
  
+ /* Support generation of DWARF2 debugging info.  */
+ #define DWARF2_DEBUGGING_INFO
+ 
  /* Don't assume anything about the header files. */
  #define NO_IMPLICIT_EXTERN_C
  
*************** Boston, MA 02111-1307, USA.  */
*** 74,79 ****
--- 77,94 ----
  /* Define the name of the .text section.  */
  #undef TEXT_SECTION_ASM_OP
  #define TEXT_SECTION_ASM_OP "\t.section .text"
+ 
+ /* How to output an unaligned integer.  */
+ #undef UNALIGNED_INT_ASM_OP
+ #define	UNALIGNED_INT_ASM_OP	"\t.long\t"
+ 
+ /* How to output an unaligned double length integer.  */
+ #undef UNALIGNED_DOUBLE_INT_ASM_OP
+ #define	UNALIGNED_DOUBLE_INT_ASM_OP	"\t.quad\t"
+ 
+ /* How to output an unaligned half length intenger.  */
+ #undef UNALIGNED_SHORT_ASM_OP
+ #define	UNALIGNED_SHORT_ASM_OP	"\t.short\t"
  
  /* Tell GCC where our standard include directory is.  */
  #undef STANDARD_INCLUDE_DIR

- Raw text -