home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.sys.apple2.gno
- Path: sparky!uunet!cs.utexas.edu!zaphod.mps.ohio-state.edu!rpi!utcsri!geac!r-node!taob
- From: taob@r-node.gts.org (Brian Tao)
- Subject: Re: cc ...
- Message-ID: <1992Dec22.141931.23764@r-node.gts.org>
- Organization: R-node Public Access UNIX Information System (416-249-5366)
- References: <behrenss.724869178@hphalle6> <1992Dec21.160930.1472@r-node.gts.org> <1h5c80INN9ba@charnel.ecst.csuchico.edu>
- Date: Tue, 22 Dec 1992 14:19:31 GMT
- Lines: 19
-
- In article <1h5c80INN9ba@charnel.ecst.csuchico.edu> jamesb@ecst.csuchico.edu (James L. Brookes) writes:
- >
- >With the current (1.2/1.3) Orca/C, if code size will exceed one
- >bank (64k) you have to segment the code into managable chunks yourself.
-
- There's one object file (main.o) that seems to fluctuate between 50
- and 62K, probably because I was playing around with different flags. I
- followed your advice last night (IRC) but I still get "Code exceeds code
- bank size" and a bunch of "Unresolved reference labels". Ah well...
-
- For those who don't know what agrep is, it's an extension of the 'grep'
- family which allows approximate matches (i.e., matches with insertions,
- deletions or substitutions). According to the docs, agrep is quite fast,
- but I haven't tried it out on the GS yet (obviously).
- --
- -- Real name: Brian Tao (Dept. of Exobiology, University of Toronto)
- -- Preferred: 90taobri@chasm.scar.utoronto.ca (checked daily)
- -- Alternate: taob@r-node.pci.on.ca (no mail over 15K, please!)
- -- """""""""""""""""""""""""
-