Xref: utzoo gnu.g++.bug:621 gnu.gcc.bug:1100
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!uxc!garcon!garcon.cso.uiuc.edu!grunwald
From: grunwald@flute.cs.uiuc.edu (Dirk Grunwald)
Newsgroups: gnu.g++.bug,gnu.gcc.bug
Subject: bug in sdbout.c, sdbout_params
Message-ID: <GRUNWALD.89May17164336@flute.cs.uiuc.edu>
Date: 17 May 89 21:43:37 GMT
Sender: news@garcon.cso.uiuc.edu
Distribution: gnu
Organization: University of Illinois, Urbana-Champaign
Lines: 48


This is w.r.t 1.35

Not certain if this is a gcc or g++ bug.

in sdbout.c, sdbout_parms, there is no check for DECL_NAME(parms) being
null, as is done in dbxout.c, dbxout_parms. The following is a guess
as to what should be done in that case; a higher level blessing is
needed.

This corrects the problem (in g++ at least) of -g0 producing lines such
as
	.def	_^R; .tag etc etc etc

However, there appears to be a remaining problem with, as the Encore assembler
puts it,

Assembler: FOO.s
        aline 392(cline 13): Unbalanced Symbol Table Entries-Too Many Scope Ends

which is unrelated to this problem, but still pretty annoying. I couldn't find
the problem from inspecting the files.

----------------------------------------------------------------------

static void
sdbout_parms (parms1)
     tree parms1;
{
  tree type;
  tree parms;

  for (parms = parms1; parms; parms = TREE_CHAIN (parms))
    {
      int current_sym_value = DECL_OFFSET (parms) / BITS_PER_UNIT;

      if (DECL_NAME(parms))
	{
	  PUT_SDB_DEF (IDENTIFIER_POINTER (DECL_NAME (parms)));
	}
      else
	{
	  PUT_SDB_DEF ("$anon");
	}
--
Dirk Grunwald
Univ. of Illinois
grunwald@flute.cs.uiuc.edu