This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: bct_p *is* used in loop.c:strength_reduction
- To: David Edelsohn <dje at watson dot ibm dot com>
- Subject: Re: bct_p *is* used in loop.c:strength_reduction
- From: Jeffrey A Law <law at cygnus dot com>
- Date: Thu, 15 Oct 1998 11:32:00 -0600
- cc: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, egcs at cygnus dot com, egcs-patches at cygnus dot com
- Reply-To: law at cygnus dot com
In message <9810151714.AA40610@marc.watson.ibm.com>you write:
> `unused'
> This attribute, attached to a variable, means that the variable is
> meant to be possibly unused. GNU CC will not produce a warning
> for this variable.
>
> I do not know what "meant to be possibly" is intended to convey. This is
> intended for cases where some compilations will not use the variable?
"possibly unused" from an optimizer standpoint means that you can't depend on
it being unused. It also sounds pretty clearly to me like it was meant to
describe the exact situation we're encountering -- we have a variable that
may or may not be used depending on a variety of compile-time decisions.
If adding an unused attribute is causing us problems, then the problem must
be elsewhere, not with the attribute itself and we should go find the real
problem instead of just disabling the unused attributes.
jeff