This is the mail archive of the
mailing list for the Cygwin project.
Re: 64bit: Possible optimizer bug in g++ 4.8.0 20130319
- From: Christian Franke <Christian dot Franke at t-online dot de>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 18 Apr 2013 18:44:25 +0200
- Subject: Re: 64bit: Possible optimizer bug in g++ 4.8.0 20130319
- References: <514CD652 dot 1010708 at t-online dot de> <20130323094033 dot GB2387 at calimero dot vinschen dot de> <CAEwic4b3dUf+rRm47mNpEz+dpFFRL-b=Qu+WUjWGVM594May0g at mail dot gmail dot com> <5151FD07 dot 3060205 at t-online dot de>
Christian Franke wrote:
Kai Tietz wrote:
2013/3/23 Corinna Vinschen schrieb:
Thanks for the testcase. I'm not a gcc expert, so I defer to Kai.
Kai, can you have a look what happens here?
yes, this is a gcc bug. it isn't sepcial to cygwin64. It happens
also for x64 mingw, so please file a regression-bug in gcc's bz. I
will take a closer look about its cause. For me it looks like that
unwinding-information doesn't reflect difference in stack-use here,
but I will need to investigate in more detail.
Done. Likely a problem with -freorder-blocks and unwinding-info:
Just for info: g++ 4.8.0-2 works as expected, 4.8-pr56742.patch was
Smartmontools now works with -O2 or -O3, even with -flto.