Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!kth!draken!ttds!jonasn
From: jonasn@ttds.UUCP (Jonas Nygren)
Newsgroups: comp.unix.ultrix
Subject: DS3100: buggy cc
Message-ID: <1207@ttds.UUCP>
Date: 3 Jun 89 02:25:59 GMT
Reply-To: jonasn@ttds.UUCP (Jonas Nygren)
Organization: The Royal Inst. of Techn., Stockholm
Lines: 44

I have seen no comments so far on the DS3100's C-compiler. I am having
lots of problems with especially pointers changing value in the middle
of a loop (there are no redundant if-statements as warned for in the 
'Release Notes for RISC processors') and the last thing that happened
is :
(dbx) r
[2] stopped at [arrow_down_button:390 ,0x402694]        arrow_button2 (self, arr
ow_down_fill,DOWN);
(dbx) n
[arrow_down_button:391 ,0x4026a8]       }
(dbx) n

Segmentation fault [arrow_down_button:391 +0x10,0x4026b8]
        }
(dbx) l 387:5
   387  arrow_down_button (self)
   388  sbarwindata * self;
   389  {
   390      arrow_button2 (self, arrow_down_fill,DOWN);
>* 391  }
(dbx)

it bombs on exit of the function. I don't do any fancy stack-fiddling,
just vanilla C, so don't blame me :-). The function is called via:

	(*object->func)(object)

I have had numerous bugs which I haven't bothered to identify, often it
will help to introduce a global temporary variable to hold the value
and in other cases it has helped to reshuffle the code. Significant is
that in all cases its pointer-values that has been affected.

My problem is that I can't figure out how to work-around these problems. 
Has anyone encountered similar problems with 'cc' on the PMAX?  Other
problems? Do you know any workarounds?

Have Digital indicated when the cc2.0 release will be available?

Yes, I have reported my problems to service but I write to the net
with a hope of speedier relief.

Jonas

Please mail responses to  jonas@softix.se  if possible.