Path: utzoo!mnetor!uunet!husc6!rutgers!rochester!bukys
From: bukys@cs.rochester.edu (Liudvikas Bukys)
Newsgroups: comp.arch
Subject: debugging on a VLIW machine
Message-ID: <8860@sol.ARPA>
Date: 21 Apr 88 14:11:39 GMT
Reply-To: bukys@cs.rochester.edu (Liudvikas Bukys)
Organization: U of Rochester, CS Dept, Rochester, NY
Lines: 7

I'm curious... to run a debugger on a Multiflow Trace, and make any sense
out of what you see, I suppose that you have to compile it with trace
scheduling and other hairy optimizations off?  Is this true?

(I suppose one could automatically intersperse debugger code between
every line of source code, and have the trace scheduler intertwine it
so that a source level debugger could still be made to work.  Is this done?)