[m-rev.] diff: always pass -fno-strict-aliasing to gcc

[Julien Fischer]

On Sat, 9 Jan 2010, Zoltan Somogyi wrote:

> On 28-Dec-2009, Julien Fischer <juliensf at csse.unimelb.edu.au> wrote:
>> 	Remove the check for whether -fno-strict-aliasing is supported.
>> 	All versions of GCC that are usable with Mercury support it.
>
> What will configure do when run on a system on which gcc does not support
> the option?

Nothing.

> Will the failure be graceful or not?

That depends upon your definition of graceful.  It will be the usual
error message that gcc gives when invoke it with a command line option
it doesn't recognise.

-fno-strict-aliasing has been supported since at least gcc 2.95 --
possibly before that, online versions of the manual prior to that are a
bit scarce -- I don't think cluttering the configure script with tests
for something that may not have been supported in versions of gcc over
10 years ago is worth it.

Julien.
--------------------------------------------------------------------------
mercury-reviews mailing list
Post messages to:       mercury-reviews at csse.unimelb.edu.au
Administrative Queries: owner-mercury-reviews at csse.unimelb.edu.au
Subscriptions:          mercury-reviews-request at csse.unimelb.edu.au
--------------------------------------------------------------------------