Re: Sun compilers: acc vs. gcc?

khb@Eng.Sun.COM (Keith Bierman)
Fri, 7 Oct 1994 17:49:23 GMT

          From comp.compilers

Related articles
Sun compilers: acc vs. gcc? cooper@holly.imsi.com (1994-10-01)
Re: Sun compilers: acc vs. gcc? harold@forsythe.stanford.edu (1994-10-03)
Re: Sun compilers: acc vs. gcc? rfg@netcom.com (1994-10-05)
Re: Sun compilers: acc vs. gcc? J.C.Highfield@loughborough.ac.uk (1994-10-06)
Re: Sun compilers: acc vs. gcc? khb@Eng.Sun.COM (1994-10-07)
Re: Sun compilers: acc vs. gcc? cord2403@cslabs2c4.engr.ccny.cuny.edu (1994-10-20)
| List of all articles for this month |

Newsgroups: comp.compilers
From: khb@Eng.Sun.COM (Keith Bierman)
Keywords: C, sparc
Organization: SunPro
References: 94-10-009 94-10-018
Date: Fri, 7 Oct 1994 17:49:23 GMT

harold@forsythe.stanford.edu (Harold Finkbeiner) writes:


      You might look into SPARCworks. With the new version it sounds like
      you can debug/edit code on the fly similiar to an interpreted version
      of C. I believe though that you require at least Solaris 2 for the new
      version which has this feature.


The 3.0.1 release runs on 4.x (Solaris 1) as well as Solaris 2. The
"fix and continue" feature you refer to works on both platforms (some
of the performance collection functionality depends on /proc, so is
disabled in the Solaris 1 release).


FWIW: It isn't an interpreter, what happens (in a nutshell) is that
            whilst debugging, one can change the source, trigger
            a recompile of that file, an automatic dlclose of the
            old symbol and a dlopen of the new version of the revised
            function. When "fixing" a relatively small function of a large
            application the effect can be very fast turnaround compared
            with the traditional edit-compile-link-debug cycle.


--
Keith H. Bierman keith.bierman@Sun.COM| khb@chiba.Eng.Sun.COM
SunSoft Developer Products |
  2550 Garcia MTV 12-40 | (415 336 2648) fax 964 0946
Mountain View, CA 94043
--


Post a followup to this message

Return to the comp.compilers page.
Search the comp.compilers archives again.