WR should use ANGLE_provoking_vertex on D3D.
Categories
(Core :: Graphics: WebRender, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox68 | --- | fixed |
People
(Reporter: jgilbert, Assigned: emilio)
References
Details
(Whiteboard: gfx-noted)
Attachments
(2 files)
Here's the incoming cherry-pick:
https://github.com/mozilla/angle/commit/0c5a74c79daf671d2a55979ae0fa467ceda991ab
Reporter | ||
Updated•7 years ago
|
Reporter | ||
Comment 2•7 years ago
|
||
I think this needs a gleam update, since it's a new (pseudo-)extension. bholley, can you assign this?
If we don't take this before the ANGLE update, it's "ok", but we'll likely get a slight startup and possible vertex shading load regression. If that's ok, we don't need to block the ANGLE update on this for 66.
Comment 3•7 years ago
|
||
I tried adding GL_ANGLE_provoking_vertex to the list at [1], but it doesn't seem to show up in the generated code. Am I doing something wrong?
Assignee | ||
Comment 4•7 years ago
|
||
gl-generator generates stuff from XML files describing the extensions, but there's none for this one, it's not magical.
We probably need to get the scripts/gl_angle_ext.xml file from ANGLE somewhere in https://github.com/brendanzab/gl-rs, and make gleam depend on an updated version of that.
Want me to do that?
Assignee | ||
Comment 5•7 years ago
|
||
I took a stab at this, https://github.com/brendanzab/gl-rs/pull/480.
With that patch to gl_generator I can add that line to gleam and I can verify the ANGLE function is being generated.
Comment 6•7 years ago
|
||
Thanks Emilio!
One question from IRC that I didn't get an answer to: do we really need to do this in Rust at all? Can't we just set it from C++ when we pass the GL Context?
Updated•7 years ago
|
Updated•7 years ago
|
Reporter | ||
Comment 7•7 years ago
|
||
Yeah, I guess we can do this in C++ land, though it feels very hacky to do it this way.
Reporter | ||
Comment 8•7 years ago
|
||
bholley: Would you prefer we do it that way? I think I can write that patch, if so.
Comment 9•7 years ago
|
||
(In reply to Jeff Gilbert [:jgilbert] from comment #8)
bholley: Would you prefer we do it that way? I think I can write that patch, if so.
I'll leave it up to Emilio.
My initial reaction is that it's not worth investing a bunch of effort into generalizing gleam to handle this case, because we're going to be moving off of gleam and onto gfx-rs in the not-too-distant future. On the other hand, it looks like emilio may have already done the work in comment 5.
Assignee | ||
Comment 10•7 years ago
|
||
I don't think it's much effort assuming my PR above is the right way to do it, but I need to get it reviewed...
Reporter | ||
Comment 11•6 years ago
|
||
Is this done then? I'm going to update ANGLE as soon in 68 as possible, and this is a blocker.
Updated•6 years ago
|
Assignee | ||
Comment 12•6 years ago
|
||
I poked in https://github.com/brendanzab/gl-rs/pull/480 again, but no response. We could either fork the crate or do it in C++, I guess. I can do the first this week if you want to go that path.
Reporter | ||
Updated•6 years ago
|
Reporter | ||
Updated•6 years ago
|
Assignee | ||
Updated•6 years ago
|
Assignee | ||
Comment 14•6 years ago
|
||
Pinged on IRC, and hoping to get that patch in during the week. Otherwise I'll use a local fork for now.
Assignee | ||
Comment 15•6 years ago
|
||
https://mozilla.logbot.info/servo/20190328#c16145376 is the relevant IRC log.
Assignee | ||
Comment 16•6 years ago
|
||
Assignee | ||
Comment 17•6 years ago
|
||
Assignee | ||
Comment 18•6 years ago
|
||
You tell me if this is right, I have no Windows build available to test :)
Depends on D25602
Assignee | ||
Updated•6 years ago
|
Comment 19•6 years ago
|
||
Reporter | ||
Comment 20•6 years ago
|
||
Sweet, thanks!
Comment 21•6 years ago
|
||
bugherder |
Description
•