On 11/23/2012 03:29 PM, Gaetano Mendola wrote:
On 11/23/2012 12:25 PM, Sergey Cheban wrote:
On 23.11.2012 12:28, Gaetano Mendola wrote:
after banging my head for an entire day I come out with this test case showing a possible bug in gcc 4.4.3 or in boost optional, the test crashes with a pure virtual method called only if compiled only with -O1, -O2, -O3. The same code in another machine with gcc 4.7.2 and boost 1.49 works fine. So, the bug you are talking about seems to be already fixed. What else do you want from the boost and gcc developers?
Sorry?
Are you suggesting to ditch gcc and/or boost released with the distribution we use, and say to our development department gcc and/or boost fixed it "by accident" on their last releases?
I would like you to consider the following, not impossible, scenario:
In boost 1.40 boost::optionals is doing something that c++ doesn't allow marked as: "if you do it the result is: 'everyone guess'". That is translated in "pure virtual function call" in gcc 4.4.3 and "no operation" in gcc 4.7.2. I would not sleep well if my own code is crashing (for no apparent reason) on a not 10 year old gcc compiler.
Now, let's make this thread a constructive thread instead to "smarty pants" here and there.
As suggested by another user I tried with gcc 4.4.3 + boost 1.50 and it crash I have tried with boost 1.52 and it crash as well. At this point or is a boost bug (not yet resolved) or a gcc bug corrected by accident or not in the new release. GCC people do release fixes on old version then it's important to submit the bug as soon we know who is faulty here.
I have submitted the bug to gcc, for any reference http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55449 Regards Gaetano Mendola