{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 乱世女痞 的问题《Is there a -ffast-math flag equivalent for the Vis》','https://www.manongdao.com/q-783113.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I'm working with the default C++ compiler (I guess it's called the "Visual Studio C++ compiler") that comes with Visual Studio 2013 with the flag /Ox (Full Optimization). Due to floating point side effects, I must disable the -ffast-math flag when using the gcc compiler. Is there an equivalent option for this flag in the configuration of the Visual Studio C++ compiler?
相关问题
- Custom controls disabled. There was an internal is
- Error building gcc 4.8.3 from source: libstdc++.so
- What are the recommended GNU linker options to spe
- What is the right order of linker flags in gcc?
- Why doesn't g++ -Wconversion warn about conver
相关文章
- Web Test recorder does not allow me to record a te
- The program '[4432] iisexpress.exe' has ex
- gcc/g++ gives me error “CreateProcess: No such fil
- Calls that precede a function's definition can
- How can I use gcc's -I command to add recursiv
- How do I know if std::map insert succeeded or fail
- How to disable CodeLens' references display in
- Breakpoint in ASP.NET MVC Razor view will not be h
None of the MSVC++ options enable the optimizations which are invoked by g++
-ffast-math.You are looking for
/fp:precise, although that is also the default.If you need the strictest floating point calculations that VS can offer, try
/fp:strict, although that is probably overkill.You probably have nothing to worry about since the default behavior should be what you desire. Just make sure that
/fp:fastis not specified, but if you try to compile with both/fp:fastand/fp:preciseyou will get a compilation error anyway, so that should be easy to catch.The link that Hans Passant provided to the MSDN website provides all the details you might want.