search for: usermisc

...k that any patches are getting applied to 1.0.5 anyway. Also, if you expect a patch to be applied, you will need to provide the changes as a patch, not as a modified copy of the source tree. The 1.2 branch includes a mechanism for private memory allocation from a static buffer. You provide a usermisc.h file that replaces the normal alloc routines. You should be able to fix most if not all of your alignment issues there, rather than putting conditionals in the main code. I do not know if it will allow you to avoid the __attribute__ directives. Look at the TI subdirectory in the main tree...

...changes as a > patch, not as a modified copy of the source tree. That's right. I won't be applying anything 1.0.5 unless it's a security issue or something like that. > The 1.2 branch includes a mechanism for private memory allocation from > a static buffer. You provide a usermisc.h file that replaces the > normal alloc routines. You should be able to fix most if not all of > your alignment issues there, rather than putting conditionals in > the main code. I do not know if it will allow you to avoid the > __attribute__ directives. Look at the TI subdirector...

...he changes as a > patch, not as a modified copy of the source tree. That's right. I won't be applying anything 1.0.5 unless it's a security issue or something like that. > The 1.2 branch includes a mechanism for private memory allocation > from a static buffer. You provide a usermisc.h file that replaces > the normal alloc routines. You should be able to fix most if not all > of your alignment issues there, rather than putting conditionals in > the main code. I do not know if it will allow you to avoid the > __attribute__ directives. Look at the TI subdirectory...

...a modified copy of the source tree. > > That's right. I won't be applying anything 1.0.5 unless it's a security > issue or something like that. > >> The 1.2 branch includes a mechanism for private memory allocation from > >> a static buffer. You provide a usermisc.h file that replaces the >> normal alloc routines. You should be able to fix most if not all of >> your alignment issues there, rather than putting conditionals in >> the main code. I do not know if it will allow you to avoid the >> __attribute__ directives. Look at th...

Hi Jean-Marc, We needed to use a release version of the SDK because this part of production code for our Sony implementations. I'm not sure how stable that branch is. Is the encoding and decoding already stable? In other words, what is not stable about that branch? Thanks, --------------------------- Saad Nader Middleware Engineer Powered By Gamespy, IGN -----Original Message----- From:

...e source tree. >> That's right. I won't be applying anything 1.0.5 unless it's a >> security issue or something like that. >> >>> The 1.2 branch includes a mechanism for private memory allocation >>> from >>> a static buffer. You provide a usermisc.h file that replaces the >>> normal alloc routines. You should be able to fix most if not all of >>> your alignment issues there, rather than putting conditionals in >>> the main code. I do not know if it will allow you to avoid the >>> __attribute__ directi...