isa/mutter
1
0
Fork 0
mirror of https://github.com/brl/mutter.git synced 2024-11-22 16:10:41 -05:00
Code Issues Packages Projects Releases Wiki Activity
9fd201ffc6
mutter/cogl/cogl-bitmap-packing.h

725 lines
21 KiB
C
Raw Normal View History

bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
/*
* Cogl
*
* An object oriented GL/GLES Abstraction/Utility Layer
*
* Copyright (C) 2012 Intel Corporation.
*
* This library is free software; you can redistribute it and/or
* modify it under the terms of the GNU Lesser General Public
* License as published by the Free Software Foundation; either
* version 2 of the License, or (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
* Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public
* License along with this library. If not, see <http://www.gnu.org/licenses/>.
*
*
*/
/* This file is included multiple times with different definitions for
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
the component_type type (either uint8_t or uint16_t). The code ends
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
up exactly the same for both but we only want to end up hitting the
16-bit path when one of the types in the conversion is > 8 bits per
component. */
/* Unpacking to RGBA */
#define UNPACK_1(b) ((b) * ((1 << (sizeof (component_type) * 8)) - 1))
#define UNPACK_2(b) (((b) * ((1 << (sizeof (component_type) * 8)) - 1) + \
1) / 3)
#define UNPACK_4(b) (((b) * ((1 << (sizeof (component_type) * 8)) - 1) + \
7) / 15)
#define UNPACK_5(b) (((b) * ((1 << (sizeof (component_type) * 8)) - 1) + \
15) / 31)
#define UNPACK_6(b) (((b) * ((1 << (sizeof (component_type) * 8)) - 1) + \
31) / 63)
#define UNPACK_10(b) (((b) * ((1 << (sizeof (component_type) * 8)) - 1) + \
511) / 1023)
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_a_8_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = 0;
dst[1] = 0;
dst[2] = 0;
dst[3] = UNPACK_BYTE (*src);
dst += 4;
src++;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_g_8_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
/* FIXME: I'm not sure if this is right. It looks like Nvidia and
Mesa handle luminance textures differently. Maybe we should
consider just removing luminance textures for Cogl 2.0 because
they have been removed in GL 3.0 */
while (width-- > 0)
{
component_type v = UNPACK_BYTE (src[0]);
dst[0] = v;
dst[1] = v;
dst[2] = v;
dst[3] = UNPACK_BYTE (255);
dst += 4;
src++;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_rgb_888_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = UNPACK_BYTE (src[0]);
dst[1] = UNPACK_BYTE (src[1]);
dst[2] = UNPACK_BYTE (src[2]);
dst[3] = UNPACK_BYTE (255);
dst += 4;
src += 3;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_bgr_888_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = UNPACK_BYTE (src[2]);
dst[1] = UNPACK_BYTE (src[1]);
dst[2] = UNPACK_BYTE (src[0]);
dst[3] = UNPACK_BYTE (255);
dst += 4;
src += 3;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_bgra_8888_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = UNPACK_BYTE (src[2]);
dst[1] = UNPACK_BYTE (src[1]);
dst[2] = UNPACK_BYTE (src[0]);
dst[3] = UNPACK_BYTE (src[3]);
dst += 4;
src += 4;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_argb_8888_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = UNPACK_BYTE (src[1]);
dst[1] = UNPACK_BYTE (src[2]);
dst[2] = UNPACK_BYTE (src[3]);
dst[3] = UNPACK_BYTE (src[0]);
dst += 4;
src += 4;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_abgr_8888_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = UNPACK_BYTE (src[3]);
dst[1] = UNPACK_BYTE (src[2]);
dst[2] = UNPACK_BYTE (src[1]);
dst[3] = UNPACK_BYTE (src[0]);
dst += 4;
src += 4;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_rgba_8888_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
dst[0] = UNPACK_BYTE (src[0]);
dst[1] = UNPACK_BYTE (src[1]);
dst[2] = UNPACK_BYTE (src[2]);
dst[3] = UNPACK_BYTE (src[3]);
dst += 4;
src += 4;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_rgb_565_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint16_t v = *(const uint16_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[0] = UNPACK_5 (v >> 11);
dst[1] = UNPACK_6 ((v >> 5) & 63);
dst[2] = UNPACK_5 (v & 31);
dst[3] = UNPACK_BYTE (255);
dst += 4;
src += 2;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_rgba_4444_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint16_t v = *(const uint16_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[0] = UNPACK_4 (v >> 12);
dst[1] = UNPACK_4 ((v >> 8) & 15);
dst[2] = UNPACK_4 ((v >> 4) & 15);
dst[3] = UNPACK_4 (v & 15);
dst += 4;
src += 2;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_rgba_5551_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint16_t v = *(const uint16_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[0] = UNPACK_5 (v >> 11);
dst[1] = UNPACK_5 ((v >> 6) & 31);
dst[2] = UNPACK_5 ((v >> 1) & 31);
dst[3] = UNPACK_1 (v & 1);
dst += 4;
src += 2;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_rgba_1010102_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t v = *(const uint32_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[0] = UNPACK_10 (v >> 22);
dst[1] = UNPACK_10 ((v >> 12) & 1023);
dst[2] = UNPACK_10 ((v >> 2) & 1023);
dst[3] = UNPACK_2 (v & 3);
dst += 4;
src += 2;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_bgra_1010102_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t v = *(const uint32_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[2] = UNPACK_10 (v >> 22);
dst[1] = UNPACK_10 ((v >> 12) & 1023);
dst[0] = UNPACK_10 ((v >> 2) & 1023);
dst[3] = UNPACK_2 (v & 3);
dst += 4;
src += 2;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_argb_2101010_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t v = *(const uint32_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[3] = UNPACK_2 (v >> 30);
dst[0] = UNPACK_10 ((v >> 20) & 1023);
dst[1] = UNPACK_10 ((v >> 10) & 1023);
dst[2] = UNPACK_10 (v & 1023);
dst += 4;
src += 2;
}
}
inline static void
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
G_PASTE (_cogl_unpack_abgr_2101010_, component_type) (const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t v = *(const uint32_t *) src;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
dst[3] = UNPACK_2 (v >> 30);
dst[2] = UNPACK_10 ((v >> 20) & 1023);
dst[1] = UNPACK_10 ((v >> 10) & 1023);
dst[0] = UNPACK_10 (v & 1023);
dst += 4;
src += 2;
}
}
#undef UNPACK_1
#undef UNPACK_2
#undef UNPACK_4
#undef UNPACK_5
#undef UNPACK_6
#undef UNPACK_10
inline static void
G_PASTE (_cogl_unpack_, component_type) (CoglPixelFormat format,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
const uint8_t *src,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
component_type *dst,
int width)
{
switch (format)
{
case COGL_PIXEL_FORMAT_A_8:
G_PASTE (_cogl_unpack_a_8_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_G_8:
G_PASTE (_cogl_unpack_g_8_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGB_888:
G_PASTE (_cogl_unpack_rgb_888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_BGR_888:
G_PASTE (_cogl_unpack_bgr_888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_8888:
case COGL_PIXEL_FORMAT_RGBA_8888_PRE:
G_PASTE (_cogl_unpack_rgba_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_BGRA_8888:
case COGL_PIXEL_FORMAT_BGRA_8888_PRE:
G_PASTE (_cogl_unpack_bgra_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ARGB_8888:
case COGL_PIXEL_FORMAT_ARGB_8888_PRE:
G_PASTE (_cogl_unpack_argb_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ABGR_8888:
case COGL_PIXEL_FORMAT_ABGR_8888_PRE:
G_PASTE (_cogl_unpack_abgr_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGB_565:
G_PASTE (_cogl_unpack_rgb_565_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_4444:
case COGL_PIXEL_FORMAT_RGBA_4444_PRE:
G_PASTE (_cogl_unpack_rgba_4444_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_5551:
case COGL_PIXEL_FORMAT_RGBA_5551_PRE:
G_PASTE (_cogl_unpack_rgba_5551_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_1010102:
case COGL_PIXEL_FORMAT_RGBA_1010102_PRE:
G_PASTE (_cogl_unpack_rgba_1010102_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_BGRA_1010102:
case COGL_PIXEL_FORMAT_BGRA_1010102_PRE:
G_PASTE (_cogl_unpack_bgra_1010102_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ARGB_2101010:
case COGL_PIXEL_FORMAT_ARGB_2101010_PRE:
G_PASTE (_cogl_unpack_argb_2101010_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ABGR_2101010:
case COGL_PIXEL_FORMAT_ABGR_2101010_PRE:
G_PASTE (_cogl_unpack_abgr_2101010_, component_type) (src, dst, width);
break;
framebuffer: Support texture based depth buffers This commit introduces some new framebuffer api to be able to enable texture based depth buffers for a framebuffer (currently only supported for offscreen framebuffers) and once allocated to be able to retrieve the depth buffer as a texture for further usage, say, to implement shadow mapping. The API works as follow: * Before the framebuffer is allocated, you can request that a depth texture is created with cogl_framebuffer_set_depth_texture_enabled() * cogl_framebuffer_get_depth_texture() can then be used to grab a CoglTexture once the framebuffer has been allocated.
2012-05-23 13:19:29 -04:00
case COGL_PIXEL_FORMAT_DEPTH_16:
case COGL_PIXEL_FORMAT_DEPTH_32:
case COGL_PIXEL_FORMAT_DEPTH_24_STENCIL_8:
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
case COGL_PIXEL_FORMAT_ANY:
case COGL_PIXEL_FORMAT_YUV:
g_assert_not_reached ();
}
}
/* Packing from RGBA */
/* Pack and round to nearest */
#define PACK_SIZE(b, max) \
(((b) * (max) + (1 << (sizeof (component_type) * 8 - 1)) - 1) / \
((1 << (sizeof (component_type) * 8)) - 1))
#define PACK_1(b) PACK_SIZE (b, 1)
#define PACK_2(b) PACK_SIZE (b, 3)
#define PACK_4(b) PACK_SIZE (b, 15)
#define PACK_5(b) PACK_SIZE (b, 31)
#define PACK_6(b) PACK_SIZE (b, 63)
#define PACK_10(b) PACK_SIZE (b, 1023)
inline static void
G_PASTE (_cogl_pack_a_8_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
*dst = PACK_BYTE (src[3]);
src += 4;
dst++;
}
}
inline static void
G_PASTE (_cogl_pack_g_8_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
/* FIXME: I'm not sure if this is right. It looks like Nvidia and
Mesa handle luminance textures differently. Maybe we should
consider just removing luminance textures for Cogl 2.0 because
they have been removed in GL 3.0 */
while (width-- > 0)
{
component_type v = (src[0] + src[1] + src[2]) / 3;
*dst = PACK_BYTE (v);
src += 4;
dst++;
}
}
inline static void
G_PASTE (_cogl_pack_rgb_888_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
dst[0] = PACK_BYTE (src[0]);
dst[1] = PACK_BYTE (src[1]);
dst[2] = PACK_BYTE (src[2]);
src += 4;
dst += 3;
}
}
inline static void
G_PASTE (_cogl_pack_bgr_888_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
dst[2] = PACK_BYTE (src[0]);
dst[1] = PACK_BYTE (src[1]);
dst[0] = PACK_BYTE (src[2]);
src += 4;
dst += 3;
}
}
inline static void
G_PASTE (_cogl_pack_bgra_8888_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
dst[2] = PACK_BYTE (src[0]);
dst[1] = PACK_BYTE (src[1]);
dst[0] = PACK_BYTE (src[2]);
dst[3] = PACK_BYTE (src[3]);
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_argb_8888_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
dst[1] = PACK_BYTE (src[0]);
dst[2] = PACK_BYTE (src[1]);
dst[3] = PACK_BYTE (src[2]);
dst[0] = PACK_BYTE (src[3]);
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_abgr_8888_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
dst[3] = PACK_BYTE (src[0]);
dst[2] = PACK_BYTE (src[1]);
dst[1] = PACK_BYTE (src[2]);
dst[0] = PACK_BYTE (src[3]);
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_rgba_8888_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
dst[0] = PACK_BYTE (src[0]);
dst[1] = PACK_BYTE (src[1]);
dst[2] = PACK_BYTE (src[2]);
dst[3] = PACK_BYTE (src[3]);
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_rgb_565_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint16_t *v = (uint16_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_5 (src[0]) << 11) |
(PACK_6 (src[1]) << 5) |
PACK_5 (src[2]));
src += 4;
dst += 2;
}
}
inline static void
G_PASTE (_cogl_pack_rgba_4444_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint16_t *v = (uint16_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_4 (src[0]) << 12) |
(PACK_4 (src[1]) << 8) |
(PACK_4 (src[2]) << 4) |
PACK_4 (src[3]));
src += 4;
dst += 2;
}
}
inline static void
G_PASTE (_cogl_pack_rgba_5551_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint16_t *v = (uint16_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_5 (src[0]) << 11) |
(PACK_5 (src[1]) << 6) |
(PACK_5 (src[2]) << 1) |
PACK_1 (src[3]));
src += 4;
dst += 2;
}
}
inline static void
G_PASTE (_cogl_pack_rgba_1010102_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t *v = (uint32_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_10 (src[0]) << 22) |
(PACK_10 (src[1]) << 12) |
(PACK_10 (src[2]) << 2) |
PACK_2 (src[3]));
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_bgra_1010102_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t *v = (uint32_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_10 (src[2]) << 22) |
(PACK_10 (src[1]) << 12) |
(PACK_10 (src[0]) << 2) |
PACK_2 (src[3]));
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_argb_2101010_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t *v = (uint32_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_2 (src[3]) << 30) |
(PACK_10 (src[0]) << 20) |
(PACK_10 (src[1]) << 10) |
PACK_10 (src[2]));
src += 4;
dst += 4;
}
}
inline static void
G_PASTE (_cogl_pack_abgr_2101010_, component_type) (const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
while (width-- > 0)
{
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint32_t *v = (uint32_t *) dst;
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
*v = ((PACK_2 (src[3]) << 30) |
(PACK_10 (src[2]) << 20) |
(PACK_10 (src[1]) << 10) |
PACK_10 (src[0]));
src += 4;
dst += 4;
}
}
#undef PACK_SIZE
#undef PACK_1
#undef PACK_2
#undef PACK_4
#undef PACK_5
#undef PACK_6
#undef PACK_10
inline static void
G_PASTE (_cogl_pack_, component_type) (CoglPixelFormat format,
const component_type *src,
Switch use of primitive glib types to c99 equivalents The coding style has for a long time said to avoid using redundant glib data types such as gint or gchar etc because we feel that they make the code look unnecessarily foreign to developers coming from outside of the Gnome developer community. Note: When we tried to find the historical rationale for the types we just found that they were apparently only added for consistent syntax highlighting which didn't seem that compelling. Up until now we have been continuing to use some of the platform specific type such as gint{8,16,32,64} and gsize but this patch switches us over to using the standard c99 equivalents instead so we can further ensure that our code looks familiar to the widest range of C developers who might potentially contribute to Cogl. So instead of using the gint{8,16,32,64} and guint{8,16,32,64} types this switches all Cogl code to instead use the int{8,16,32,64}_t and uint{8,16,32,64}_t c99 types instead. Instead of gsize we now use size_t For now we are not going to use the c99 _Bool type and instead we have introduced a new CoglBool type to use instead of gboolean. Reviewed-by: Neil Roberts <neil@linux.intel.com> (cherry picked from commit 5967dad2400d32ca6319cef6cb572e81bf2c15f0)
2012-04-16 16:56:40 -04:00
uint8_t *dst,
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
int width)
{
switch (format)
{
case COGL_PIXEL_FORMAT_A_8:
G_PASTE (_cogl_pack_a_8_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_G_8:
G_PASTE (_cogl_pack_g_8_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGB_888:
G_PASTE (_cogl_pack_rgb_888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_BGR_888:
G_PASTE (_cogl_pack_bgr_888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_8888:
case COGL_PIXEL_FORMAT_RGBA_8888_PRE:
G_PASTE (_cogl_pack_rgba_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_BGRA_8888:
case COGL_PIXEL_FORMAT_BGRA_8888_PRE:
G_PASTE (_cogl_pack_bgra_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ARGB_8888:
case COGL_PIXEL_FORMAT_ARGB_8888_PRE:
G_PASTE (_cogl_pack_argb_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ABGR_8888:
case COGL_PIXEL_FORMAT_ABGR_8888_PRE:
G_PASTE (_cogl_pack_abgr_8888_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGB_565:
G_PASTE (_cogl_pack_rgb_565_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_4444:
case COGL_PIXEL_FORMAT_RGBA_4444_PRE:
G_PASTE (_cogl_pack_rgba_4444_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_5551:
case COGL_PIXEL_FORMAT_RGBA_5551_PRE:
G_PASTE (_cogl_pack_rgba_5551_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_RGBA_1010102:
case COGL_PIXEL_FORMAT_RGBA_1010102_PRE:
G_PASTE (_cogl_pack_rgba_1010102_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_BGRA_1010102:
case COGL_PIXEL_FORMAT_BGRA_1010102_PRE:
G_PASTE (_cogl_pack_bgra_1010102_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ARGB_2101010:
case COGL_PIXEL_FORMAT_ARGB_2101010_PRE:
G_PASTE (_cogl_pack_argb_2101010_, component_type) (src, dst, width);
break;
case COGL_PIXEL_FORMAT_ABGR_2101010:
case COGL_PIXEL_FORMAT_ABGR_2101010_PRE:
G_PASTE (_cogl_pack_abgr_2101010_, component_type) (src, dst, width);
break;
framebuffer: Support texture based depth buffers This commit introduces some new framebuffer api to be able to enable texture based depth buffers for a framebuffer (currently only supported for offscreen framebuffers) and once allocated to be able to retrieve the depth buffer as a texture for further usage, say, to implement shadow mapping. The API works as follow: * Before the framebuffer is allocated, you can request that a depth texture is created with cogl_framebuffer_set_depth_texture_enabled() * cogl_framebuffer_get_depth_texture() can then be used to grab a CoglTexture once the framebuffer has been allocated.
2012-05-23 13:19:29 -04:00
case COGL_PIXEL_FORMAT_DEPTH_16:
case COGL_PIXEL_FORMAT_DEPTH_32:
case COGL_PIXEL_FORMAT_DEPTH_24_STENCIL_8:
bitmap-fallback: Support converting all pixel format types _cogl_bitmap_fallback_convert now supports converting to and from all of the pixel formats, except it continues to preserve the premult status of the original bitmap. The pixels are unpacked into a temporary buffer that is either 8-bits per component or 16-bits per component RGBA depending on whether the destination format is going to use more than 8 bits per component (eg RGBA_1010102). The packing and unpacking code is stored in a separate header which is included twice to generate the functions needed for both sizes of unpacked data. The hope is that when converting between two formats that are both 8-bit sized, such as swizzling between BGRA and RGBA, then the multiplications and divisions in the code will be optimized out and it shouldn't be too inefficient. Previously the inner switch statement to decide which conversion to use only operated on one pixel at a time so it was probably relatively slow. Reviewed-by: Robert Bragg <robert@linux.intel.com>
2012-02-29 10:16:27 -05:00
case COGL_PIXEL_FORMAT_ANY:
case COGL_PIXEL_FORMAT_YUV:
g_assert_not_reached ();
}
}
Reference in New Issue Copy Permalink