Joe Pep wrote:
> Can anyone tell me how to turn off the 'warnings being treated as
> errors' option ?
Remove the -Werror option.

Or better, just fix the warnings! The warning you have may be benign
(although At91GetPllClock will unnecessarily add to the size of your
code), but warnings are usually either errors or poor coding practice -
an error waiting to happen.

There are many less brutal methods of fixing this one warning (not least
simply removing the unused code!)

The warning is switched on by the use of -Wall, so you could also remove
that and still retain the -Werror; but you will suppress a number of
useful warning types. Rather than using -Wall, you could switch on
individual warning options. See
http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Warning-Options.html#Warning-Options
for details of the warning options and which ones -Wall switches on.

You can suppress the "unused" warning for variables (but not functions)
by using an 'unused' attribute.
(http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Variable-Attributes.html#Variable-Attributes)

If for some reason you want the At91GetPllClock code to remain but are
not using it for the moment, you could wrap it in conditional
compilation:

#if defined USE_AT91GETPLLCLOCK
int At91GetPllClock()
{
...
}
#endif

and then use a -DUSE_AT91GETPLLCLOCK option when you need the code.

Another way of 'fixing' the warning is to make a dummy reference. In the
case of a function, (I assume from its name At91GetPllClock is a
function), this requires care because you don't want to call the
function and you don't want the optimizer to warn of unreachable code,
so:

int main()
{
    volatile dummy = 0 ;
    if( dummy )
    {
        At91GetPllClock() ;
    }

    ....
}

The code above will create a reference that is never called, but the
volatile declaration stops the optimizer from determining that it can
never be called. This has the advantage that the dummy code need not be
removed if you later add a real reference to At91GetPllClock.

One final way of avoiding this warning is to place At91GetPllClock in a
static library and link to that. The linker will only add the code to
your program if it is explicitly referenced, but it is still available
at any time. You could also place At91GetPllClock in a separate module
and simply not use it in this build.

Clifford

Thanks much, Clifford.

I hope one day to be 1/2 as well versed as you obviously are with gcc
and all its features and options.
I had already 'used' the function 'At91GetPllClock' by making a dummy
call to it
and did get full compilation, but you've given some good insight for
other alternatives. The pointer to the gcc help pages is also much
appreciated.

Thanks again.

Joe


Clifford Slocombe wrote:
> Joe Pep wrote:
>> Can anyone tell me how to turn off the 'warnings being treated as
>> errors' option ?
> Remove the -Werror option.
>
> Or better, just fix the warnings! The warning you have may be benign
> (although At91GetPllClock will unnecessarily add to the size of your
> code), but warnings are usually either errors or poor coding practice -
> an error waiting to happen.
>
> There are many less brutal methods of fixing this one warning (not least
> simply removing the unused code!)
>
> The warning is switched on by the use of -Wall, so you could also remove
> that and still retain the -Werror; but you will suppress a number of
> useful warning types. Rather than using -Wall, you could switch on
> individual warning options. See
> http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Warning-Options.html#Warning-Options
> for details of the warning options and which ones -Wall switches on.
>
> You can suppress the "unused" warning for variables (but not functions)
> by using an 'unused' attribute.
> 
(http://gcc.gnu.org/onlinedocs/gcc-4.1.2/gcc/Variable-Attributes.html#Variable-Attributes)
>
> If for some reason you want the At91GetPllClock code to remain but are
> not using it for the moment, you could wrap it in conditional
> compilation:
>
> #if defined USE_AT91GETPLLCLOCK
> int At91GetPllClock()
> {
> ...
> }
> #endif
>
> and then use a -DUSE_AT91GETPLLCLOCK option when you need the code.
>
> Another way of 'fixing' the warning is to make a dummy reference. In the
> case of a function, (I assume from its name At91GetPllClock is a
> function), this requires care because you don't want to call the
> function and you don't want the optimizer to warn of unreachable code,
> so:
>
> int main()
> {
>     volatile dummy = 0 ;
>     if( dummy )
>     {
>         At91GetPllClock() ;
>     }
>
>     ....
> }
>
> The code above will create a reference that is never called, but the
> volatile declaration stops the optimizer from determining that it can
> never be called. This has the advantage that the dummy code need not be
> removed if you later add a real reference to At91GetPllClock.
>
> One final way of avoiding this warning is to place At91GetPllClock in a
> static library and link to that. The linker will only add the code to
> your program if it is explicitly referenced, but it is still available
> at any time. You could also place At91GetPllClock in a separate module
> and simply not use it in this build.
>
> Clifford