Mail Archives: djgpp/2003/04/14/01:27:32
On Sunday 13 April 2003 17:41, Rob Kramer wrote:
> Hi,
>
> On second thought, I'm trying to build a c/c++ cross compiler, not a native
> DOS executable. I think this means most of the patches in gcc322s2.zip are
> not required for me, since almost all seem to be related to fixing DOS
> things (c++ -> cxx, fix paths, etc).
>
> One I'm not sure about:
>
> *** sdbout.c~1 Mon Sep 16 17:52:54 2002
> --- sdbout.c Mon Sep 16 18:17:42 2002
> ***************
> *** 853,859 ****
> name = IDENTIFIER_POINTER (DECL_ASSEMBLER_NAME (decl));
>
> if (GET_CODE (value) == MEM
> ! && GET_CODE (XEXP (value, 0)) == SYMBOL_REF)
> {
> PUT_SDB_DEF (name);
> if (TREE_PUBLIC (decl))
> --- 853,861 ----
> name = IDENTIFIER_POINTER (DECL_ASSEMBLER_NAME (decl));
>
> if (GET_CODE (value) == MEM
> ! && GET_CODE (XEXP (value, 0)) == SYMBOL_REF
> ! && GET_CODE (XEXP (XEXP (value, 0), 0)) != PLUS
> ! && GET_CODE (XEXP (XEXP (value, 0), 0)) != MINUS)
> {
> PUT_SDB_DEF (name);
> if (TREE_PUBLIC (decl))
>
> I have no idea what this does, but this seems to be the only patch not
> directly DOS compiler related.
There are still patches related to some bug reports I have submitted. As far
as I remeber this was related assembler warning messages when COFF
debugging info is requested for Fortran program which uses COMMON blocks are
being used.
A different patch were applied for upcomming gcc-3.3 that fix this problem.
But it's was not applied for gcc-3.2.2.
Also the default now is DWARF2 debugging info. COFF debugging info support is
perhaps rather botroted.
>
> If I don't have to rebuild configures etc, the rest of the process should
> be reasonable standard (ahem)..
Andris
- Raw text -