Re: [PATCH] gcc3/ld patch for direct-linking-to-dll and auto-import support

Hi Ralf, > while compiling trolltechs qt/xfree library with gcc3 (3.2x) on > cygwin I recognized, that the auto-import stuff in combination of > recent ld does not work in case of const variables in a dll when > using direct linking to a dll, because gcc put those variables into > a readonly, that

Re: HELP! How to add secrel psuedo op for pe-i386?

Hi Brian, > > So, all I need to do is define ASM_OUTPUT_DWARF_OFFSET correctly in > > gcc/config/i386/cygwin.h. > > > > Does anyone have a good way to define a section relative offset in > > assembly for Cygwin, or do I need to define labels for the sections in the > > link script and use them? T

Re: Support for DDWARF-2 debug info? (on Cygwin)

Hi Brian, > My current problem is that all previous DWARF2 implementations > assign a VMA of zero to the .debug_* sections in the link script. > This violates the PE format and makes the executable unusable. I saw your post about this to the binutils list. Does the PE format require that the deb

Re: Support for DDWARF-2 debug info? (on Cygwin)

Hi Brian, > The coff versions of sec_to_styp_flags and styp_to_sec_flag in bfd > look to see if the section name begins with .debug and modify the > section flags appropriately. The PE versions do not even look at > the section name. Ahh, yes, you are right. I guess that no-one has tried to inc

Re: Support for DDWARF-2 debug info? (on Cygwin)

Hi Brian, > I have built gcc 3.2.1 (just --enable-languages=c so far) with > "#define DWARF2_DEBUGGING_INFO 1" added to config/i386/cygwin.h. > The resulting compiler still produces stabs by default, but will > accept "-gdwarf-2". > > When using "-gdwarf-2", the debug information is, I believe, >