On Mon, Jul 13, 2020 at 6:46 AM Hans-Peter Nilsson wrote:
>
> > From: Richard Biener
> > Date: Tue, 7 Jul 2020 09:00:22 +0200
>
> > On Tue, Jul 7, 2020 at 6:03 AM Hans-Peter Nilsson via Gcc-patches
> > wrote:
> > >
> > > We say very little about reads and writes to aggregate /
> > > compound
> From: Richard Biener
> Date: Tue, 7 Jul 2020 09:00:22 +0200
> On Tue, Jul 7, 2020 at 6:03 AM Hans-Peter Nilsson via Gcc-patches
> wrote:
> >
> > We say very little about reads and writes to aggregate /
> > compound objects, just scalar objects (i.e. assignments don't
> > cause reads). Let's
> From: Martin Sebor
> Date: Wed, 8 Jul 2020 02:09:37 +0200
> On 7/6/20 10:02 PM, Hans-Peter Nilsson via Gcc-patches wrote:
> > We say very little about reads and writes to aggregate /
> > compound objects, just scalar objects (i.e. assignments don't
> > cause reads). Let's lets say something
On 7/6/20 10:02 PM, Hans-Peter Nilsson via Gcc-patches wrote:
We say very little about reads and writes to aggregate /
compound objects, just scalar objects (i.e. assignments don't
cause reads). Let's lets say something safe about aggregate
objects, but only for those that are the same size as
On Tue, Jul 7, 2020 at 6:03 AM Hans-Peter Nilsson via Gcc-patches
wrote:
>
> We say very little about reads and writes to aggregate /
> compound objects, just scalar objects (i.e. assignments don't
> cause reads). Let's lets say something safe about aggregate
> objects, but only for those that
We say very little about reads and writes to aggregate /
compound objects, just scalar objects (i.e. assignments don't
cause reads). Let's lets say something safe about aggregate
objects, but only for those that are the same size as a scalar
type.
There's an equal-sounding section (Volatiles) in
