bct_p *is* used in loop.c:strength_reduction

[David Edelsohn]

>>>>> Jeffrey A Law writes:

Jeff> "possibly unused" from an optimizer standpoint means that you can't depend on
Jeff> it being unused.  It also sounds pretty clearly to me like it was meant to
Jeff> describe the exact situation we're encountering -- we have a variable that
Jeff> may or may not be used depending on a variety of compile-time decisions.

	When we were adding these types of attributes to rs6000.c, we went
to the extreme of two different declarations for the two different ifdef
cases -- one using the parameters, the other not.

	If this attribute is not dangerous and we want to use it in this
manner just to remove warnings and not to imply anything to the compiler,
then that is fine with me.  However, as part of this process of adding
these attributes and removing warnings, we have implemented two different
policies of how and where to use them.  We should be consistent about
using this attribute throughout EGCS to avoid this type of confusion.

David