This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

[PATCH] Fix issues with flag_strict_aliasing changing during compilation (PR c/37106, take {2,3})

From: Jakub Jelinek <jakub at redhat dot com>
To: Richard Guenther <richard dot guenther at gmail dot com>
Cc: gcc-patches at gcc dot gnu dot org
Date: Mon, 3 Nov 2008 21:23:26 +0100
Subject: [PATCH] Fix issues with flag_strict_aliasing changing during compilation (PR c/37106, take {2,3})
References: <20081103153344.GJ14706@tyan-ft48-01.lab.bos.redhat.com> <84fc9c000811030801r1fc63ceevf90ffc54d8f79556@mail.gmail.com>
Reply-to: Jakub Jelinek <jakub at redhat dot com>

On Mon, Nov 03, 2008 at 05:01:45PM +0100, Richard Guenther wrote:
> Hmm.  I do not like this too much.  For 4.4 I'd like us simply avoid
> changing flag_strict_aliasing.

Attached are 2 alternatives to do that.  One that just silently avoids
changing flag_strict_aliasing, one that does that silently for
__optimize__({0,1,2,3}), but errors on __optimize__("fstrict-aliasing")
when -fno-strict-aliasing is given (or vice versa).

>  For 4.5 we should move flag_strict_aliasing to struct function instead.

How would that change anything?

	Jakub

Attachment: Y089a
Description: Text document

Attachment: Y089b
Description: Text document

Follow-Ups:
- Re: [PATCH] Fix issues with flag_strict_aliasing changing during compilation (PR c/37106, take {2,3})
  - From: Richard Guenther

References:
- [PATCH] Fix issues with flag_strict_aliasing changing during compilation (PR c/37106)
  - From: Jakub Jelinek
- Re: [PATCH] Fix issues with flag_strict_aliasing changing during compilation (PR c/37106)
  - From: Richard Guenther

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]