search for: 000265

Displaying 4 results from an estimated 4 matches for "000265".

Did you mean: 0.0265
2020 Apr 06
2
F18 ready to be merged + preview of merge
...oveCarriageReturns Whilst removing code that manipulated C-style strings we hit upon a case which seemed to show that std::remove_if was a regression on certain targets over the current algorithm using C standard memmove. This flang-dev thread<http://lists.llvm.org/pipermail/flang-dev/2020-April/000265.html> summarises the situation and we are gathering further data before deciding what to do. We propose to continue to investigate this and make any necessary changes after F18 becomes part of the monorepo. [4] Doxygen infrastructure We are still working through the final comments on this patch...
2020 Apr 07
3
F18 ready to be merged + preview of merge
...oveCarriageReturns Whilst removing code that manipulated C-style strings we hit upon a case which seemed to show that std::remove_if was a regression on certain targets over the current algorithm using C standard memmove. This flang-dev thread<http://lists.llvm.org/pipermail/flang-dev/2020-April/000265.html> summarises the situation and we are gathering further data before deciding what to do. We propose to continue to investigate this and make any necessary changes after F18 becomes part of the monorepo. [4] Doxygen infrastructure We are still working through the final comments on this patch...
2020 Apr 07
3
F18 ready to be merged + preview of merge
...t; Whilst removing code that manipulated C-style strings we hit upon a case > which seemed to show that std::remove_if was a regression on certain > targets over the current algorithm using C standard memmove. This flang-dev > thread <http://lists.llvm.org/pipermail/flang-dev/2020-April/000265.html> > summarises the situation and we are gathering further data before deciding > what to do. We propose to continue to investigate this and make any > necessary changes after F18 becomes part of the monorepo. > > > > [4] Doxygen infrastructure > > We are still work...
2005 Sep 27
4
problems understanding yuv_buffer format
hi folks! once again i am trying to decode a yuv_buffer to a 24 bit RGB buffer. last time nobody seemed willing to tell me how to do this, so i am trying again. i try to make my questions more simple. what i need to know is: how many bytes are in each y, u, v array? what for are these strides? what exactly is a "plane" in a frame, and what does it do? what i want to achieve is