Confirmed users
396
edits
Platform/GFX/2011-August-15: Difference between revisions
m
→Minutes: use {{bug|nnn}} template, wiki link
(→Agenda) |
m (→Minutes: use {{bug|nnn}} template, wiki link) |
||
| (5 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
* Every Monday at 2:30 PM Pacific/5:30 PM Eastern/21:30 UTC/Tuesday at 9:30 AM NZDT | *Every Monday at 2:30 PM Pacific/5:30 PM Eastern/21:30 UTC/Tuesday at 9:30 AM NZDT | ||
* +1 650 903 0800 x92 Conf# 99366 | *+1 650 903 0800 x92 Conf# 99366 | ||
* +1 800 707 2533 (pin 369) Conf# 99366 (toll free, Skype) | *+1 800 707 2533 (pin 369) Conf# 99366 (toll free, Skype) | ||
* Video (Vidyo) link: https://v.mozilla.com/flex.html?roomdirect.html&key=DeP4hnHU6nlN | *Video (Vidyo) link: https://v.mozilla.com/flex.html?roomdirect.html&key=DeP4hnHU6nlN | ||
* Vidyo room 9366 (if you have LDAP and can log in at https://v.mozilla.com) | *Vidyo room 9366 (if you have LDAP and can log in at https://v.mozilla.com) | ||
= | = Minutes = | ||
<ul><li>Should the Cairo update be backed out? (jrmuizel) <ul><li>Chris Jones points out that a lot of mobile bugs and even some X bugs were fixed by the Cairo update. The biggest set of fennec problems was worked around by {{bug|637828}} though.</li | |||
><li>jrmuizel doesn't want to back out, and cjones strongly doesn't want to back out.</li | |||
><li>It doesn't really seem like the bugs are severe enough to warrant a backout. Jeff will continue fixing the bugs.</li | |||
><li>The crash bug is most severe, but we understand it.</li | |||
><li>dependent bugs: {{bug|666893}}</li></ul | |||
></li | |||
><li>Azure update (Bas) <ul><li>Thebes wrapper depends on the Cairo D2D backend, and therefore will be a little delayed.</li | |||
><li>Joe's going to work on the Cairo D2D backend this week.</li | |||
><li>Azure on Fx7?<ul><li>There's one semi-rare crash that we can't reproduce ({{bug|676690}}). We might be able to work around it, though.</li | |||
><li>ClearType isn't supported in Azure. We made this choice on purpose to speed things up for the implementation of Azure-D2D. There are various mitigation strategies, including using the Cairo implementation of canvas in moz-opaque situations.</li | |||
><li>Bas to collect regressions and link them to the original Azure D2D bug ({{bug|651858}}).</li></ul | |||
></li></ul | |||
></li | |||
><li>D3D9 TP4 regression (benwa) <ul><li>{{bug|660264}}</li | |||
><li>Two issues:<ul><li>System patch(es) (windows, drivers, directx) should fix the regression.<ul><li>We know the union of all the patches available fixes this Tp4 regression. What we don't know is which specific patch or subset of patches fixes the regression.</li | |||
><li>We took an educated guess that it was the driver update, and we were wrong.</li | |||
><li>Current guess is windows update</li | |||
><li>Will check out a talos machine to confirm</li></ul | |||
></li | |||
><li>The regression isn't seen on tp5</li></ul | |||
></li></ul | |||
></li | |||
><li>Cross-process D3D10 landed (cjones)<ul><li>Context given here: [[Electrolysis/Short_Terms_Goals]]</li | |||
><li>{{bug|648484}}</li | |||
><li>landed, stuck this time</li | |||
><li>follow-up bugs for proper synchronization linked above; painting is racy right now</li | |||
><li>needs performance analysis</li | |||
><li>security review tentatively proposed for Sept. 13th, 1000 PDT</li | |||
><li>OpenGL sharing on Mac is still an open problem, but /should/ work out of the box. Needs mac-specific optimizations though<ul><li>Nominations for victim: BenWa or mattwoodrow</li></ul | |||
></li></ul | |||
></li | |||
><li>WebGL Antialiasing update (jgilbert) <ul><li>Down to one webgl conformace suite regression</li></ul | |||
></li | |||
><li>For the love of all that is holy, book your all-hands travel if you are going to it. (joe)<ul><li>Friday is the last day, though it may be less structured than the other days. 4pm-ish looks to be the last scheduled time.</li></ul | |||
></li | |||
><li>TestPilot DirectWrite font rendering survey (joe/jdaggett)<ul><li>John to email Jono today.</li></ul | |||
></li | |||
><li>Web3D Community Working Group (Bas)<ul><li>There is a group of people from Web3D (the group that originated with VRML) who are working on a declarative 3D web standard.</li | |||
><li>http://www.x3dom.org/x3dom/w3c/charter/ - W3C Incubator group for the nascent standard.</li | |||
><li>Bas thinks we should send a representative to the working group in order to steer it towards something that we feel better with.</li | |||
><li>Bas will go. No one else is very interested/believes in it</li></ul | |||
></li | |||
><li>SIGGRAPH wrap-up (Bas, joe)<ul><li>Scaleform<ul><li>Triangulation with 1 pixel border for AA (sounds the same as D2D)</li | |||
><li>Batching is important (retained-mode API)</li></ul | |||
></li | |||
><li>GPUs continue to execute branches in the "old style" - that is, masking off the ALUs that missed the branch, and executing in lock step across the entire SIMD unit.<ul><li>This has different implications depending on the architecture. NVIDIA is bigger but wider (eg ~16-32 threads executing on the same processor); AMD the opposite.</li></ul | |||
></li | |||
><li>Web3D consortium has implemented a bunch of things on top of WebGL</li | |||
><li>Deferred shading via cached fragments on every triangle; gets shading down to about 1-2x per pixel vs 20+</li | |||
><li>If you have any questions, desire for citations or desire for a paper, please contact Joe <joe@mozilla.com><br/><br | |||
/></li></ul | |||
></li></ul | |||
> | |||