Bug#930119: gcc-8: __dso_handle place in wrong segment on ia64

Jason Duerstock <[email protected]>
Newsgroups gmane.linux.debian.ports.ia64
Message-ID <155991452813.8801.16162481043461940572.reportbug__18883.7886483938$1559914771$gmane$org@netsvcs1.gallaudet.edu>
Package: gcc-8
Version: 8.3.0-7
Severity: normal
Tags: patch
User: [email protected]
Usertags: ia64

Dear Maintainer,

On ia64, __dso_handle is placed in .data/.bss rather than .sdata/.sbss,
causing a link failure on at least one package (libphonenumber).  The
patch has been added to trunk here:

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

A PR has also been opened but for some reason does not reflect the trunk
change.

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

Thank you.

-- System Information:
Debian Release: 10.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: ia64

Kernel: Linux 5.0.0-trunk-mckinley (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gcc-8 depends on:
ii  binutils      2.31.1-16
ii  cpp-8         8.3.0-7
ii  gcc-8-base    8.3.0-7
ii  libc6.1       2.28-2
ii  libcc1-0      9-20190428-1
ii  libgcc-8-dev  8.3.0-7
ii  libgcc1       1:9-20190428-1
ii  libgmp10      2:6.1.2+dfsg-4
ii  libisl19      0.20-2
ii  libmpc3       1.1.0-1
ii  libmpfr6      4.0.2-1
ii  libstdc++6    9-20190428-1
ii  libunwind8    1.2.1-9
ii  zlib1g        1:1.2.11.dfsg-1

Versions of packages gcc-8 recommends:
ii  libc6.1-dev  2.28-2

Versions of packages gcc-8 suggests:
pn  gcc-8-doc         <none>
pn  gcc-8-locales     <none>
pn  libasan5-dbg      <none>
pn  libatomic1-dbg    <none>
pn  libgcc1-dbg       <none>
pn  libgomp1-dbg      <none>
pn  libitm1-dbg       <none>
pn  liblsan0-dbg      <none>
pn  libmpx2-dbg       <none>
pn  libquadmath0-dbg  <none>
pn  libtsan0-dbg      <none>
pn  libubsan1-dbg     <none>

-- no debconf information
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.