WARNING:angle_platform_impl.cc(51)] : rx::HLSLCompiler::compileToBinary(228): C:\fakepath(31,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(37,8-27): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them
Reported by
mikhail....@gmail.com,
Sep 15 2017
|
|||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3215.0 Safari/537.36 Steps to reproduce the problem: check chrome://gpu/ and see follow messages: WARNING:angle_platform_impl.cc(51)] : rx::HLSLCompiler::compileToBinary(228): C:\fakepath(31,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(37,8-27): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them What is the expected behavior? What went wrong? messages: WARNING:angle_platform_impl.cc(51)] : rx::HLSLCompiler::compileToBinary(228): C:\fakepath(31,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(37,8-27): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them I think what this is abnormal Did this work before? N/A Chrome version: 63.0.3215.0 Channel: canary OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: Shockwave Flash 27.0 r0
,
Sep 19 2017
Tested the issue on windows 7 using chrome stable M61 #61.0.3163.91 and M63 #63.0.3215.0 and latest canary M63 #63.0.3218.3 and issue is not reproduced. Chrome://gpu doesn't have any errors and everything is okay. Attached screencast for reference. @mikhail.v.gavrilov-- Could you please try in latest canary and if you can still able to repro , please proivde us the detailed steps to reproduce the issue. Thanks!
,
Sep 20 2017
Thank you for providing more feedback. Adding requester "hdodda@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Oct 5 2017
,
Oct 10 2017
Requesting someone from the GPU team to look into this issue for further triaging. Thanks!
,
Oct 13 2017
Could you have a look please?
,
Oct 13 2017
This is a benign shader warning. We should at some point either figure out if this is an ANGLE bug, or is a case of undefined behaviour. If it is undefined, we can always fix the offending shader (likely a compositor or rasterization/Skia shader somewhere). Lowering priority since it isn't user-visible aside from the about:gpu page.
,
Oct 13 2017
CC'ing Olli, who has a lot of expertise in the HLSL transpiler component of ANGLE.
,
Dec 14 2017
I can no longer reproduce this in Canary. Olli did you inadvertently fix this warning with your integer pow workaround fix, or another CL?
,
Dec 14 2017
I don't think the pow workaround fix should have affected this. Maybe the compositor or skia shader causing the issue got fixed?
,
Dec 20 2017
Yeah, verified it's still happening.
,
Dec 25 2017
Google chrome version 65.0.3303.0 Message: [6372:7144:1225/100532.319:WARNING:angle_platform_impl.cc(59)] : compileToBinary(228): C:\fakepath(46,8-58): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them C:\fakepath(50,8-27): warning X3571: pow(f, e) will not work for negative f, use abs(f) or conditionally handle negative values if you expect them still present on chrome://gpu/ tab, but this issue have status Fixed. Why?
,
Dec 28 2017
Sorry, was a mistake. Should not have been marked fixed.
,
Oct 9
|
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by mikhail....@gmail.com
, Sep 15 2017162 KB
162 KB View Download