This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: [PATCH] Disable optimization for volatile object
- From: Richard Guenther <richard dot guenther at gmail dot com>
- To: Eric Botcazou <ebotcazou at adacore dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Wed, 22 Apr 2009 21:32:15 +0200
- Subject: Re: [PATCH] Disable optimization for volatile object
- References: <200904222130.20623.ebotcazou@adacore.com>
On Wed, Apr 22, 2009 at 9:30 PM, Eric Botcazou <ebotcazou@adacore.com> wrote:
> Hi,
>
> gimplify_modify_expr_rhs can decide to directly propagate a constructor from
> the DECL_INITIAL of the RHS of assignment to the LHS of the assignment. ?It
> doesn't do it if the RHS is volatile but it shouldn't do it either if the LHS
> is volatile as the assignment might end up being done on a per-field basis.
>
> Tested on i586-suse-linux, OK for mainline?
Ok. Can you add a simple testcase?
Thanks,
Richard.
>
> 2009-04-22 ?Eric Botcazou ?<ebotcazou@adacore.com>
>
> ? ? ? ?* gimplify.c (gimplify_modify_expr_rhs) <VAR_DECL>: Do not do a direct
> ? ? ? ?assignment from the constructor either if the target is volatile.
>
>
> --
> Eric Botcazou
>