Bug 864914

Summary: gstreamer-1.0 should be compiled with higher memory alignment (16byte or higher)
Product: [openSUSE] openSUSE 13.1 Reporter: Forgotten User Mfp5y7JP5V <forgotten_Mfp5y7JP5V>
Component: BasesystemAssignee: E-mail List <gnome-bugs>
Status: RESOLVED WONTFIX QA Contact: E-mail List <qa-bugs>
Severity: Enhancement    
Priority: P5 - None CC: dimstar, pgajdos, zaitor
Version: Final   
Target Milestone: ---   
Hardware: All   
OS: openSUSE 13.1   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Forgotten User Mfp5y7JP5V 2014-02-20 16:41:22 UTC
User-Agent:       Mozilla/5.0 (X11; Linux i686) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/31.0.1650.63 Safari/537.36 SUSE/31.0.1650.63

I'm writing plugins for gstreamer using SIMD instructions. These plugins crash all the time since the gst buffer data is memory aligned on 8 bytes instead of 16 bytes. Would it be possible to compile the next gstreamer plugins with higher memory alignment? 

Reproducible: Always

Steps to Reproduce:
1. install gstreamer-1.0 with plugins etc.
2. write a custom plugin and print out the buffer data pointer; you will notice that it is not 16byte aligned
Actual Results:  
plugin crash (segfault)
Comment 1 Petr Gajdos 2015-03-12 10:36:12 UTC
Reassigning to maintainer/bugowner to consider it.

See --with-memory-alignment.
Comment 2 Dominique Leuenberger 2015-03-12 10:39:49 UTC
I think that's something we should discuss with upstream to ensure we don't introduce other issues... having a plugin that depends on compiler flags which are not the default as provided by the upstream project sounds like a very bad idea.
Comment 3 Tomáš Chvátal 2018-04-12 13:33:40 UTC
This version of openSUSE changed to end-of-life (EOL [1]) status. As such
it is no longer maintained, which means that it will not receive any
further security or bug fix updates.
As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
openSUSE, or consider the bug still valid, please feel free to reopen this
bug against that version, or open a new ticket.

Thank you for reporting this bug and we are sorry it could not be fixed
during the lifetime of the release.

[1] https://en.opensuse.org/Lifetime