This is the mail archive of the gcc@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]
Other format: [Raw text]

SMS parameters


The following sms parameters exist.

max-sms-loop-number
sms-max-ii-factor
sms-dfa-history
sms-loop-average-count-threshold

None of these are documented in invoke.texi.

The first one is odd, as its help string says,
  "Maximum number of loops to perform swing modulo scheduling on \
	  (mainly for debugging)"
and its implementation is via a static counter that counts bbs in a *program*

  static int passes = 0;
  ...
  FOR_EACH_BB (bb)
     ...
     /* For debugging.  */
     if ((passes++ > MAX_SMS_LOOP_NUMBER) && (MAX_SMS_LOOP_NUMBER != -1))

it doesn't look like a particularly sensible thing to expose.  If
it must be exposed, it should probably be called 'sms-max-loop-number'.
Notice the fence-post error there, we'll actually schedule 1 more
than MAX_SMS_LOOP_NUMBER.

nathan
--
Nathan Sidwell    ::   http://www.codesourcery.com   ::     CodeSourcery LLC
nathan@codesourcery.com    ::     http://www.planetfall.pwp.blueyonder.co.uk


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