Many thanks for these responses. We'll want to discuss some of them
further, but, before we do, survey responses from any other GCC
developers would be very welcome, especially from those who know the
analysis and optimisation code. (So far GCC is relatively
under-represented in our data; we hav
On Fri, 17 Apr 2015, Peter Sewell wrote:
> [1/15] How predictable are reads from padding bytes?
> If you zero all bytes of a struct and then write some of its members, do
> reads of the padding return zero? (e.g. for a bytewise CAS or hash of
> the struct, or to know that no security-relevant da
On 17 April 2015 at 17:03, wrote:
> On 04/17/2015 09:01 AM, Peter Sewell wrote:
>>
>> On 17 April 2015 at 15:19, wrote:
>>>
>>>
On Apr 17, 2015, at 9:14 AM, Peter Sewell
wrote:
Dear gcc list,
we are trying to clarify what behaviour of C implementations is
act
On 04/17/2015 09:01 AM, Peter Sewell wrote:
On 17 April 2015 at 15:19, wrote:
On Apr 17, 2015, at 9:14 AM, Peter Sewell wrote:
Dear gcc list,
we are trying to clarify what behaviour of C implementations is
actually relied upon in modern practice, and what behaviour is
guaranteed by curren
On 17 April 2015 at 15:19, wrote:
>
>> On Apr 17, 2015, at 9:14 AM, Peter Sewell wrote:
>>
>> Dear gcc list,
>>
>> we are trying to clarify what behaviour of C implementations is
>> actually relied upon in modern practice, and what behaviour is
>> guaranteed by current mainstream implementations
> On Apr 17, 2015, at 9:14 AM, Peter Sewell wrote:
>
> Dear gcc list,
>
> we are trying to clarify what behaviour of C implementations is
> actually relied upon in modern practice, and what behaviour is
> guaranteed by current mainstream implementations (these are quite
> different from the ISO
