[Bug 1815057] Re: [UBUNTU] GCC Wrong code generate for floating point workloads Ubuntu 18.04

[Launchpad Bug Tracker]

This bug was fixed in the package gcc-7 - 7.4.0-5ubuntu1

---------------
gcc-7 (7.4.0-5ubuntu1) disco; urgency=medium

  * Merge with Debian; remaining changes:
    - Build from upstream sources.

gcc-7 (7.4.0-5) unstable; urgency=medium

  * Update to SVN 20190209 (r268732) from the gcc-7-branch.
    - Fix PR target/88856 (S390X). Addresses: #915738. LP: #1815057.
    - Fix PR target/85755 (PPC), PR target/87064 (PPC), PR target/87064 (PPC),
      PR fortran/67679, PR fortran/88393, PR libfortran/88678,
      PR target/88343 (PPC).

 -- Matthias Klose <doko at ubuntu.com>  Sat, 09 Feb 2019 23:19:08 +0100

** Changed in: gcc-7 (Ubuntu)
       Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to gcc-8 in Ubuntu.
https://bugs.launchpad.net/bugs/1815057

Title:
  [UBUNTU] GCC Wrong code generate for floating point workloads Ubuntu
  18.04

Status in Ubuntu on IBM z Systems:
  In Progress
Status in gcc-7 package in Ubuntu:
  Fix Released
Status in gcc-8 package in Ubuntu:
  Fix Released
Status in gcc-7 source package in Bionic:
  New
Status in gcc-8 source package in Bionic:
  New
Status in gcc-7 source package in Cosmic:
  New
Status in gcc-8 source package in Cosmic:
  New

Bug description:
  An IBM Z GCC backend problem leads to wrong code being generated for
  some floating point workloads.

  https://gcc.gnu.org/bugzilla/show_bug.cgi?id=88856

  A patch has been committed to the GCC 7 and 8 upstream branch and
  needs to be picked up for the Ubuntu 18.04 compiler.

  https://gcc.gnu.org/viewcvs/gcc?view=revision&revision=268551

  This change might require rebuilding floating point related packages.
  Although the actual problem is hard to trigger. I could only reproduce
  it in case if conversion introduces load on condition instructions in
  the ce2 pass. The testcase I've looked into came from the python scipy
  package which builds with -funroll-loops. The load on condition
  opportunity in that case was introduced with the RTL loop unrolling.
  This made the split1 pass to use the problematic splitter generating
  wrong code in the end.

  According to https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=915738

  The patch has been picked up for gcc-8 8.2.0-18 already

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1815057/+subscriptions