[FFmpeg-trac] #872(avutil:new): av_rescale_q returns wrong 64bits in arm cortex-a8 processor

[FFmpeg]

#872: av_rescale_q returns wrong 64bits in arm cortex-a8 processor
--------------------------------------+-----------------------------------
             Reporter:  kaijun61      |                    Owner:  michael
                 Type:  defect        |                   Status:  new
             Priority:  important     |                Component:  avutil
              Version:  git-master    |               Resolution:
             Keywords:  av_rescale_q  |               Blocked By:
             Blocking:                |  Reproduced by developer:  0
Analyzed by developer:  0             |
--------------------------------------+-----------------------------------

Comment (by cehoyos):

 Replying to [comment:19 kaijun61]:
 > I feel confused about ffmpeg and libav. Before and including
 http://git.videolan.org/?p=ffmpeg.git;a=commit;h=a85ce653fb14ae968419453fabf1ffe10d1f15df
 commit, both repos. look same.

 For several months, there is one (of several) forks of FFmpeg that is
 known to contain many (>100) regressions over FFmpeg. Since some of those
 bugs in this fork are possibly security-relevant, we strongly recommend
 only to use FFmpeg from http://ffmpeg.org (which you can download from the
 videolan server). The FFmpeg tree also contains the complete history of
 this fork, but there should be no reason for you to use it, the commit you
 quote above does come from the mentioned fork, the correct version to test
 would be 48706f41 (the subsequent commit):
 http://git.videolan.org/?p=ffmpeg.git;a=commit;h=48706f41e1a17e04b0aa09852eff021833708233

 > But from this snap, I don't see mathematics.h included. But its previous
 one and one after two commits, i.e. one you want me to look at have
 mathematics.h. Also after this snap, both libav and ffmpeg have different
 commits.

 Can you tell me if you can reproduce the problem you described above with
 FFmpeg git head (or any released version)?

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/872#comment:20>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker