I don't think so. This just refers to generally accepting TEXTURE_CUBE_MAP_ARRAY for these calls. It does however not refer to specific compressed formats, which is what the core spec bit is about (what this really wanted to forbid there is specifying TEXTURE_3D).
Roland Am 15.05.2015 um 19:05 schrieb Marek Olšák: > From ARB_texture_cube_map_array: > > Accepted by the <target> parameter of TexImage3D, TexSubImage3D, > CompressedTeximage3D, CompressedTexSubImage3D and CopyTexSubImage3D: > > TEXTURE_CUBE_MAP_ARRAY_ARB > > So the extension spec "fixes" the core spec. > > Marek > > On Fri, May 15, 2015 at 4:49 AM, Roland Scheidegger <srol...@vmware.com> > wrote: >> Accidentally, I stumbled upon this bit in gl 4.5, chapter 8.7 >> "Compressed Texture Images": >> "An INVALID_OPERATION error is generated by CompressedTexImage3D if >> internalformat is one of the EAC, ETC2, or RGTC formats and either >> border is non-zero, or target is not TEXTURE_2D_ARRAY." >> This forbids TEXTURE_CUBE_MAP_ARRAY as a target. >> Doesn't look like that's what mesa implements, nor does it make sense. >> This has to be a spec bug, right? >> >> Roland >> _______________________________________________ >> mesa-dev mailing list >> mesa-dev@lists.freedesktop.org >> https://urldefense.proofpoint.com/v2/url?u=http-3A__lists.freedesktop.org_mailman_listinfo_mesa-2Ddev&d=AwIBaQ&c=Sqcl0Ez6M0X8aeM67LKIiDJAXVeAw-YihVMNtXt-uEs&r=Vjtt0vs_iqoI31UfJxBl7yv9I2FeiaeAYgMTLKRBc_I&m=HgJD3ol4T_ZdKio1CDuIebSrsd6IsqyVrt8xMgAGKU8&s=jR6XbmLF6OuiV0cZ4kLNbL9fIKsTA3CnOD7vdYw3kQg&e= >> _______________________________________________ mesa-dev mailing list mesa-dev@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/mesa-dev
