Thank you for the report. Since I don't deal with the GL stack, I've passed your question to the relevant team.
I can confirm we determined this to be a driver issue. Our GL driver team is now working on a fix.
We have fixed this issue internally. The bug should no longer reproduce in the next driver release, or the one that follows.
Define "next driver release", because since this comment 2 drivers came out, and still no fix.
Installed Relive driver, still not fixed. So "next driver release" = half year\1 year later ?