On Mon, Jan 12, 2009 at 10:50 PM, Raoul Gough wrote:
> Richard Guenther wrote:
>>
>> On Mon, Jan 12, 2009 at 12:03 AM, Raoul Gough
>> wrote:
>>
>>>
>>> Richard Guenther wrote:
>>>
>
> [snip]
This is also invalid. You have to use placement new to change the
dynamic
type of mem
Richard Guenther wrote:
On Mon, Jan 12, 2009 at 12:03 AM, Raoul Gough wrote:
Richard Guenther wrote:
[snip]
This is also invalid. You have to use placement new to change the dynamic
type of memory.
Yes, I guess that makes sense. I've modified the example like this:
#includ
On Mon, Jan 12, 2009 at 12:03 AM, Raoul Gough wrote:
> Richard Guenther wrote:
>>
>> On Sun, Jan 11, 2009 at 7:59 PM, Raoul Gough
>> wrote:
>>
>
> [snip]
>>>
>>> I guess the situation is more complicated in C++, which has explicit
>>> destructors. Consider the following example, which is getting
Richard Guenther wrote:
On Sun, Jan 11, 2009 at 7:59 PM, Raoul Gough wrote:
[snip]
I guess the situation is more complicated in C++, which has explicit
destructors. Consider the following example, which is getting closer to the
problem that originally got me interested in this subject:
voi
On Sun, Jan 11, 2009 at 7:59 PM, Raoul Gough wrote:
> Richard Guenther wrote:
>>
>> On Sat, Jan 10, 2009 at 12:55 PM, Richard Guenther
>> wrote:
>>
>>>
>>> On Sat, Jan 10, 2009 at 12:19 PM, Raoul Gough
>>> wrote:
>>>
>
> [snip]
Here we pass into bar a pointer to int and double at the s
Richard Guenther wrote:
On Sat, Jan 10, 2009 at 12:55 PM, Richard Guenther
wrote:
On Sat, Jan 10, 2009 at 12:19 PM, Raoul Gough wrote:
[snip]
Here we pass into bar a pointer to int and double at the same storage
location. So now, if the compiler goes ahead and reorders the read and w
On Sat, Jan 10, 2009 at 12:55 PM, Richard Guenther
wrote:
> On Sat, Jan 10, 2009 at 12:19 PM, Raoul Gough wrote:
>> I've been investigating a code-reordering question to do with g++ strict
>> alias analysis, and I suspect there is a deficiency in the way type-based
>> alias analysis works. I real
On Sat, Jan 10, 2009 at 12:19 PM, Raoul Gough wrote:
> I've been investigating a code-reordering question to do with g++ strict
> alias analysis, and I suspect there is a deficiency in the way type-based
> alias analysis works. I realise that's unlikely to be the case, so I'll try
> to present a c
I've been investigating a code-reordering question to do with g++ strict
alias analysis, and I suspect there is a deficiency in the way
type-based alias analysis works. I realise that's unlikely to be the
case, so I'll try to present a concise demonstration which uses (I
think) well-defined C c
