GLEW 1.9.0 has also been released which includes support for OpenGL 4.3

Wow! That was the quickest GLEW update in history

Disclaimer: This is my personal profile. Whatever I write here is my personal opinion and none of my statements or speculations are anyhow related to my employer and as such should not be treated as accurate or valid and in no case should those be considered to represent the opinions of my employer.
Technical Blog: http://www.rastergrid.com/blog/

Just tried out glObjectLabel(), and it doesn't work with GL_BUFFER or GL_TEXTURE - it throws an INVALID_ENUM for both (at least the feedback is nice: "GL_INVALID_ENUM error generated. ObjectLabel: invalid <identifier> enum value"). I also tried GL_TEXTURE_2D just in case, but this didn't work either (nor should it, from the spec).

It works with GL_FRAMEBUFFER, GL_PROGRAM and GL_SHADER, though - at least it doesn't throw a GL error. However, a later performance message "Program/shader state performance warning: Fragment Shader is going to be recompiled because the shader key based on GL state mismatches." doesn't reference my shader name at all, which seems to defeat the purpose. It'd also be nice to know what part of the GL state it's referring to.

I installed NVIDIA beta driver 304.32 on Lubuntu 12.04 Linux using the xorg-edgers PPA so that I wouldn't have to fool with .run scripts and turning off X servers. On my laptop I have an old GeForce 8600M GT card, which is OpenGL 3.3 class HW. The NVIDIA OpenGL driver page says, "For OpenGL 3 capable hardware, these new extensions are provided:" and gives a list of 18 extensions. Unfortunately none of them are shown as available by either glxinfo or nvidia-settings.

Anyone have OpenGL 3 class HW that's showing the new extensions, on either Windows or Linux?

It appears we missed support for GL_TEXTURE, GL_FRAMEBUFFER and GL_RENDERBUFFER. All the others are supported. This is a trivial fix and it'll be in the next beta update next week. Sorry for the trouble and thanks for reporting the bug.

We'll also audit our error messages and make sure they use the object label instead of the number if it exists. This fix will come later. The extension is still useful because middleware tools can query objects to get names which the app sets. But clearly having the names in the debug_output strings makes sense.

What is the best way to file a bug report to NVIDIA for their beta drivers? I used their generic "Submit feedback on an NVIDIA product" form, but the release notes for the driver direct one to an NVIDIA developer site. This site seems to be isolated from the main NVIDIA site; the developer area reached from the main site is different. I used to have an NVIDIA developer account eons ago, but it seems that has lapsed. I don't see any obvious way to create an account for the nvdeveloper.nvidia.com site, and it doesn't accept the username and password I have for the main site. So, I have the feeling that the left hand is separated from what the right hand is doing, and nobody's actually going to read the feedback I just filed. What's the best way?