|Re: [eigen] Matrix product crashes when compiled with MSVC 2010 in release|
[ Thread Index |
| More lists.tuxfamily.org/eigen Archives
- To: eigen@xxxxxxxxxxxxxxxxxxx
- Subject: Re: [eigen] Matrix product crashes when compiled with MSVC 2010 in release
- From: Hauke Heibel <hauke.heibel@xxxxxxxxxxxxxx>
- Date: Fri, 13 Aug 2010 17:53:23 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=OFFbKUs3y3qdE0Y0aBUyQxvtpXbB36tPm2RdkAPdtME=; b=AatLwzuy68O2b2c+nUpPD9bPlW8Nj288ZN8vXfOgSjpU4WehQIyYg/PpEiX8wI9PjZ rv6oMcU0NDg8IyXggGsN5IjWnyzFlYVmonsmyRdPBvV9SlC7FlOQxGN8VNB8+FHFNMbM HcrOZKMLj/+2rgM9rYH0GPm14nHhae7g/O+Ew=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=areZyjrpiQqWZ+rGctx//azQ85MMireXX7VLNYS9RPeEN8RjV+3NRUzufkUBy8Scev xosc+rBz54Z14/9QDqTn6bV8NWQGXehvF3YvKoRt2IPf91OtRVKEe8z3sqHl5/y2iRZj 6/b6jFLQyRgJtXC77lF+aOaUYlk8t/zj65NCg=
no idea how to write volatile inline assembly on MSVC. Normal inline
assembly did not help - it helps if I set that function to "don't
inline" but that will kill the run-time and I assume any other patch
will kill the run-time too. I am clueless for the moment.
On Fri, Aug 13, 2010 at 4:16 PM, Ilya Baran <baran37@xxxxxxxxx> wrote:
> The reason I ran into this is that CMake creates projects without
> whole program optimization by default. I can, of course, live with
> enabling whole program optimization--the problem is that the entire
> code has to be reoptimized when a single cpp file changes (this is
> slow even for a moderate-sized project). I think it makes sense to
> spend a little effort on working around this (the asm idea seems
> promising) because other people will hit it, but I agree that it's not
> a good idea to introduce a runtime performance regression for this.
>>> Just a short question to you Ilya - do you rely on disabling the whole
>>> program optimization? Per default it is enabled if you create a new
>>> solution. That's why we never hit that issue so far. I am saying for
>>> all our unit tests, the compiler settings are mostly on default for
>>> MSVC builds. Testing against all combinations of compiler settings is
>>> not really possible. ;)
>> Spot on!
>> Even if the people at everyone's favorite corporation are not very
>> responsive to bug reports, I would still say it's about the only thing
>> to do about it, unless Hauke finds an applicable work-around!