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: law at cygnus dot com
- Subject: Re: bct_p *is* used in loop.c:strength_reduction
- From: Jason Merrill <jason at cygnus dot com>
- Date: 15 Oct 1998 12:17:38 -0700
- Cc: David Edelsohn <dje at watson dot ibm dot com>, "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>, egcs at cygnus dot com, egcs-patches at cygnus dot com
- References: <13081.908471190@hurl.cygnus.com>
>>>>> Jeffrey A Law <law@cygnus.com> writes:
> In message <9810151702.AA40664@marc.watson.ibm.com>you write:
>> I have removed the ATTRIBUTE_UNUSED designation from the bct_p
>> parameter in loop.c:strength_reduce(). That parameter *is* used depending
>> on ifdef's.
> An ATTRIBUTE_UNUSED shouldn't cause problems if the parameter is actually
> used. At least that's been my understanding. I've always been under the
> impression that it meant the varable/parameter *might* be unused, not that
> is absolutely is unused and you can optimize based on that information.
Right. It actually works by setting TREE_USED on the decl.
Jason