I have committed the original change. Let me know if there is a problem
Best,
-Rick
gbl...@eecs.umich.edu wrote:
Sorry for not responding sooner. I thought Rick was going to commit his
change.
This is the bit of code that traces the macroop on request. For that to
happen,
ExecMacro needs
I think your change is right, but just in case could you please try tracing with
different combinations of turning on and explicitly off Exec, ExecMicro, and
ExecMacro? I sent an email recently which talked about how the new options
work.
My compiler must not have that warning, but I have seen
It's a warning that was introduced with gcc 4.3, and we have warnings
cause errors. When I ported the tree to gcc 4.3, I chose to keep the
warning (there was some debate) because we're supporting so many users
now that some of them might not be so savvy on the particulars of
operator precedence.
