Re: Compiler bug with aligned members in virtuals + alloca() in VS
Why do you need `alloca'? From the short sample you provided
it's not obvious that `alloca' is necessary. It can be
easily replaced by regular `operator new':
virtual bool Application::render()
{
ClassWithDestructor classWithDestructor;
std::auto_ptr<int> myInt(new int);
AlignedMember alignedMember;
return true;
}
Then, does anyone know what the next step is for submitting
this as a bug to Microsoft?
There is Feedback Connections at MS site. However, I didn't
find anything for VS2003.NET.
"Available Connections"
http://connect.microsoft.com/availableconnections.aspx
HTH
Alex
Hi Alex,
Thanks for your feedback.
I'll totally agree in the contrived example, I don't need alloca() but in
real world situations, the overhead of operator new is excessive relative to
the locality of the allocation and the lifetime of the array. I use the
simple alloca() in the example since it was the minimum case that broke the
compiler.
The connections site doesn't really give me any options for VS 2003/.Net
either. This is pretty much what I found when I was looking into posting this
bug, that there's not a lot of options when it comes to reporting issues with
the older version of VS. For now I'll have to use MSC_VER >= 1400 to check
for VS 2005 to enable code that would cause issues with 2003.
Thanks again,
Rich