Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.lang.c Subject: Re: C Compiler bugs Message-ID: <8055@brl-smoke.ARPA> Date: 9 Jun 88 02:49:25 GMT References: <15367@tut.cis.ohio-state.edu> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 13 In article <15367@tut.cis.ohio-state.edu> lvc@tut.cis.ohio-state.edu (Lawrence V. Cipriani) writes: >The *fixed* crt0.o >must have been recoded to recognize arbitrary return values. That would be a pretty neat trick! Some linkers are able to detect interface type mismatches and issue a warning, which would catch the kind of error under discussion, but I haven't yet seen an AT&T CCS (aka SGS) linker that does that. Perhaps the "fix" was simply that the error did not have catastrophic results when the way struct values are returned was changed, or something like that.