This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: profiling on the c4x



  In message <199810250930.JAA04776@htbrug.net.HCC.nl>you write:
  > Hello,
  > 
  > The code in profile.c does not handle a JUMP_INSN inside a PARALLEL.
  > This insn is generated on the c4x for the repeat_block_end.
  > The definition for the repeat_block_end is (from c4x.md):
I'm going to suggest we hold off teaking the profile code which builds cfgs.

If we're going to change it, we should instead change it to use the cfg
computed by flow.c instead of having it compute the cfg on its own (and
incorrectly I might add).

I don't think it'd be all that hard to fix profile.c to use the pred/succ
lists provided by flow.  Look at haifa-sched.c::build_control_flow.  It's been
on my todo list for a while...  Similarly for reg-stack.c.




jeff


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]