1. 11 4月, 2020 7 次提交
    • F
      modify some op for dyg rcnn (#23648) · 0a878be8
      FDInSky 提交于
      * test=develop modify some op for dyg rcnn
      0a878be8
    • C
      Add bce_loss op (#23388) · ab05cdc4
      ceci3 提交于
      * add bce_loss
      
      * fix mistake
      
      * replace paddle_enforce,test=develop
      
      * fix,test=develop
      
      * update,test=develop
      
      * remove duplicate,test=develop
      
      * update,test=develop
      
      * update error,test=develop
      
      * update,test=develop
      
      * fix unittest, test=develop
      
      * update, test=develop
      ab05cdc4
    • M
      [DNNL][INT8][FP32] MatMul (#23395) · a63bcf9a
      Michał Gallus 提交于
      * Initial FP32 DNNL MatMul Implementation
      
      * Implement int8 DNNL MatMul
      
      * Unify in-kernel-naming, clean UTs
      
      * MatmuL: Introduce op caching
      
      * Final adjustments
      
      test=develop
      
      * Remove dy_graph disablement
      
      test=develop
      
      * Change dnnl header name to new one
      
      test=develop
      
      * Contrain multi head check to prevent fails
      
      test=develop
      
      * Resolve dnnl header problems on MAC CI
      
      * Variable namings to kernel and skip_grad_ci added
      
      test=develop
      
      * Prevent MAC CI from failing
      
      * Prevent windows build from failing
      
      test=develop
      
      * Modify UTs to conform to the rules
      
      * Modify MatMul aux functions namings
      
      test=develop
      a63bcf9a
    • C
      remove logging setting, test=develop (#23715) · a2315d37
      Chen Weihang 提交于
      a2315d37
    • W
      Fix the matmul test case, avoid double and float precision diff · 05476e9f
      wawltor 提交于
      reduce the pricision of test case for matmul
      05476e9f
    • H
      Temporary Disable Flaky test_cond Under Windows (#23424) · 4c57e395
      Huihuang Zheng 提交于
      The flaky windows test is hard to debug. It just has an exit code 0xc0000374 without any log so we don't know where and why. The probability of failure is about 1/50.
      
      I spent 3 days and found it happened only when using PE + control flow + Windows. Exit code 0xc0000374 indicates heap corruption or access violation, but I found the memory is enough during debugging. There is no failed test under 500+ linux tests. I suspect the reason is multiple thread difference between Windows and Linux but I don't have time to completely debug it now. I will temporary disable the test and fix it in next days.
      4c57e395
    • Z
  2. 10 4月, 2020 33 次提交