craig@macbeth.Princeton.EDU (Craig Kolb) (07/24/87)
I have a ray-tracing program that I'm trying to get to run in finite time on
a 3B2/310 running SVR2.1 Using "cc" (and loading with -f), I get an
executable that runs, but is painfully slow. Using "fpcc", I get a smaller
executable that doesn't run because it's "too big". The scoop:
tracer: 34824 + 4236 + 723024 = 762084
tracerfp: 23488 + 3656 + 722916 = 750060
Anybody have any clue what the story is? I've reconfigured the kernel so
that MAXMEM is 2048 (* 2K), so this baby SHOULD run. (In fact, I've got
CTeX running (compiled with 'cc'), which is well over 1M...) What could be
different between fpcc and cc such that tracerfp won't exec?
Thanks!
--
Craig Kolb
UUCP: {princeton, astrovax}!macbeth!craig 51 Woodmere Drive
ARPA: craig@macbeth.Princeton.EDU Sudbury, MA 01776
"If Reagan is the answer, it must have been a *very* silly question."