[gstreamer-bugs] [Bug 545714] GST_READ_UINT_* and GST_WRITE_UINT_* are not always safe to use

[GStreamer (bugzilla.gnome.org)]

If you have any questions why you received this email, please see the text at
the end of this email. Replies to this email are NOT read, please see the text
at the end of this email. You can add comments to this bug at:
  http://bugzilla.gnome.org/show_bug.cgi?id=545714

  GStreamer | gstreamer (core) | Ver: HEAD CVS

Sebastian Dröge changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |slomo at circular-chaos.org




------- Comment #6 from Sebastian Dröge  2008-08-01 12:47 UTC -------
I don't think you could measure any difference if the inline memcpy() variants
are used as gcc at least compiles this to single instructions on x86/amd64.

Well, on x86 the 64 variants are of course compiled to shift&or...


What would be that advantage of the shift&or variants over the memcpy() ones?
IIRC gcc optimizes them to single instructions too if possible.


-- 
See http://bugzilla.gnome.org/page.cgi?id=email.html for more info about why you received
this email, why you can't respond via email, how to stop receiving
emails (or reduce the number you receive), and how to contact someone
if you are having problems with the system.

You can add comments to this bug at http://bugzilla.gnome.org/show_bug.cgi?id=545714.