This bug was fixed in the package gcc-8 - 8-20180414-1ubuntu1

gcc-8 (8-20180414-1ubuntu1) bionic; urgency=medium

  * GCC 8 snapshot, taken from the trunk 20180408 (r259224).
  * Strip the binaries for the upcoming release.

gcc-8 (8-20180414-1) unstable; urgency=medium

  * GCC 8 snapshot, taken from the trunk 20180414 (r259383).

  [ Matthias Klose ]
  * Update GDC to 20180410.
  * Don't install i586 symlinks anymore for i386 builds in sid.
  * Fix zlib-dev dependencies for the libphobos cross multilib packages.
  * Fix dependency generation for libatomic and libquadmath cross packages.
  * Use triplet-prefixed as and ld (Helmut Grohne). Closes: #895251.
  * Link libasan, liblsan, libubsan always with --no-as-needed. LP: #1762683.
  * Use --push-state --as-needed and --pop-state instead of --as-needed and
    --no-as-needed for linking libgcc.
  * Update the gcc-foffload-default patch. LP: #1721355.

  [ Svante Signell ]
  * Reintroduce libgo patches for hurd-i386. Closes: #894080.

 -- Matthias Klose <>  Sat, 14 Apr 2018 07:29:59 +0200

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

You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

  MALLOC_PERTURB_=117 gcc -v gives strange output for

To manage notifications about this bug go to:

ubuntu-bugs mailing list

Reply via email to