This is the mail archive of the
mailing list for the GCC project.
Re: [PATCH] reimplement -fstrict-volatile-bitfields v4, part 2/2
- From: DJ Delorie <dj at redhat dot com>
- To: Sandra Loosemore <sandra at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, richard dot guenther at gmail dot com, bernd dot edlinger at hotmail dot de
- Date: Mon, 30 Sep 2013 16:18:30 -0400
- Subject: Re: [PATCH] reimplement -fstrict-volatile-bitfields v4, part 2/2
- Authentication-results: sourceware.org; auth=none
- References: <52463D60 dot 8040607 at codesourcery dot com>
As per my previous comments on this patch, I will not approve the
changes to the m32c backend, as they will cause real bugs in real
hardware, and violate the hardware's ABI. The user may use
-fno-strict-volatile-bitfields if they do not desire this behavior and
understand the consequences.
I am not a maintainer for the rx and h8300 ports, but they are in the
To reiterate my core position: if the user defines a proper "volatile
int" bitfield, and the compiler does anything other than an int-sized
access, the compiler is WRONG. Any optimization that changes volatile
accesses to something other than what the user specified is a bug that
needs to be fixed before this option can be non-default.