search for: removecarriagereturn

...ld like to handle all cases together which also means coming up with a good system for reporting ICEs. See these code review comments<https://github.com/flang-compiler/f18/issues/966> for details. We propose to start fresh on this work after F18 becomes part of the monorepo. [3] remove_if vs RemoveCarriageReturns 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> s...

...ld like to handle all cases together which also means coming up with a good system for reporting ICEs. See these code review comments<https://github.com/flang-compiler/f18/issues/966> for details. We propose to start fresh on this work after F18 becomes part of the monorepo. [3] remove_if vs RemoveCarriageReturns 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> s...

...r which also means coming up with a good system for reporting ICEs. > See these code review comments > <https://github.com/flang-compiler/f18/issues/966> for details. We > propose to start fresh on this work after F18 becomes part of the monorepo. > > > > [3] remove_if vs RemoveCarriageReturns > > 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/20...