Vs2005 Beta and Profile Guided Optimizations

[Andre Lorbach]

Hi all,

I hope I picked up the right group
A few days ago I installed the VS2005 Beta and started playing with
it.

First of all the (Profile Guided Optimizations) PGO Feature looks very
cool
After some reading and testing, I got it to work. I followed this
article:
http://whidbey.msdn.microsoft.com/l...1b-ec8c-4626-9c29-fa5ffb6f27f8.asp?frame=true

I created an Instrumented Version, run it and then created an
Optimized Version of my app.

All this seemed to work well, this is the optimize compiler output:
------ Build started: Project: MyProject, Configuration: Release Win32
------
Linking...
Merging <somewhere>\Release\MyProject!1.pgc
Generating code
1280 of 1280 (100.00%) profiled functions will be compiled for speed
Finished generating code
Merging manifest files...
Build log was saved at "file://<somewhere>\Release\BuildLog.htm"
Syslog - 0 error(s), 0 warning(s)
----------

The instrumented were running fine.
With the same appliaction configuration, the optimized version just
silent crashes after 5-10 seconds no matter what I do :|!
I know this is a beta and a very new feature but maybe someone here
has some help for me.

Maybe it is because I am running a 2Cpu System. Some of my System
details:
Windows XP SP2
2 x AMD Operon 244 (1,8 Ghz)
2 GB Ram
VS2003 and VS2005 Beta (From MSDN) installed.

Thanks for help - best regards,
Andre Lorbach
Adiscon

 

[Brandon Bray [MSFT]]

With the same appliaction configuration, the optimized version just
silent crashes after 5-10 seconds no matter what I do :|!
I know this is a beta and a very new feature but maybe someone here
has some help for me.

Given the information available, there are too many possibilities of what
could be wrong. Aggressive optimization does not necessarily mean there is a
bug in the compiler.

If you feel comfortable sharing your project with us, we can investigate.

 

[Andre Lorbach]

Given the information available, there are too many possibilities of what
could be wrong. Aggressive optimization does not necessarily mean there is a
bug in the compiler.

If you feel comfortable sharing your project with us, we can investigate.

Thanks for your answer. It only crashes under stress circumstances.
I will analyze it further, it could be a bug in my code which just
didn't popup yet. The app is using multithreading and in my test where
it crashed, I had both CPU's at full usage. I will continue playing
around with this new optimization stuff and come back again when I
find the problem

 

[Steve McLellan]

"Brandon Bray [MSFT]" <[email protected]> wrote in message

Andre Lorbach wrote: []
If you feel comfortable sharing your project with us, we can

investigate.

Thanks for your answer. It only crashes under stress circumstances.
I will analyze it further, it could be a bug in my code which just
didn't popup yet. The app is using multithreading and in my test where
it crashed, I had both CPU's at full usage. I will continue playing
around with this new optimization stuff and come back again when I
find the problem

Multithreaded apps are notoriously hard to debug when you get intermittent
faults. Make sure any resources that need to be are thread-safe, and make
sure the calls you're making from different threads are safe too. Bob
Powell's FAQ is a great resource for multithreading under .NET. Good luck!

Steve

 

[Ioannis Vranos]

Bob
Powell's FAQ is a great resource for multithreading under .NET. Good luck!

May you provide a URL?

 

[Steve McLellan]

luck!


May you provide a URL?

Hi,

Apologies, it's Jon Skeet's FAQ.
http://www.yoda.arachsys.com/csharp/multithreading.html

Sorry for not posting the link, very busy at the moment.

Steve