Displaying 2 results from an estimated 2 matches for "q1jw".
Did you mean:
q1j
2006 Apr 20
0
Major internal changes, TI DSP build change
...???E????+??3????????R?,?M?peJ;?
??(??Q?6??
?_???a?????7?"r?}(??h?????vS?7?k1?g7u?????ML????+Y?K?????&N??????m%
z}WI???J\i?i?<@b???A???R?
~^z??FF?%%?f?$
???Pc}???
}??$??O????-$?1??%???<`H??.j??.??^?=???B?c8e?r+?(??_??R?Fb???'??o???
Um?????6???M
???xz?E?Y?????Zh?????b????H?ab?%aS{%q1jw
?Mro%aN?6$6V"9?m??'???SY??T4?!??
????}?Q3% ???|
T??=?????G
??m????(?tbE(Rm?hB?
?d?D19l?h???'?.??D\?5I4Y2?Ht?'l?D?`6??A?pJn?????????6?????G??L?{???????oh??=??Ul?PKx?[3????cspeex_config_types.h?UMo?6?? ?M??n?
vO?D?dI%?$>i?? ??!????w?r??&E/?!1??y???????n_Z????,:?/??_A??????7???...
2006 Apr 19
2
Major internal changes, TI DSP build change
> You found it. The SHL32 (not SHR32) line fixes the problem. It must be
> doing a 16-bit shift, then extending the result (which is reasonable). As
> it happens, that it the same macro which gave us trouble last May
> (25th/26th), when the C55 build was more subtlely broken.
Yes, that's what I finally remembered. I think I've fixed all
occurrences (by adding EXTEND32)