This is the mail archive of the binutils@sourceware.org mailing list for the binutils project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

ld fails to build proper executables in several cases on x64_64-w64-mingw32


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

I first discovered this by bootstrapping gcc and running the
testsuite. I got around 1200 new failures for the same gcc revision
using binutils-2.26 compared to using binutils-2.25.1, see
https://gcc.gnu.org/ml/gcc-testresults/2016-01/msg02756.html
and
https://gcc.gnu.org/ml/gcc-testresults/2016-01/msg02757.html

Most failures in the libstdc++ testsuite, 954 additional failures.

Besides the new failures, some tests which PASS and a some which FAIL
allocate huge memory spaces, over 40 GByte.

So I tried to analyze a bit. I picked a test case from the libstdc++
testsuite 22_locale/locale/cons/6.cc. Checking the preprocessed
source, the assemply and the object files for the support library and
the test case itself there's no difference. I disabled all debug
information for an easier comparison. The objects are identical for
both versions.

The culprit is the linker, I opened a bug report, which includes a
test case, see https://sourceware.org/bugzilla/show_bug.cgi?id=19531

Any idea what's going wrong here?

Rainer

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCAAGBQJWqz68AAoJEB3HOsWs+KJbWOoH+gOEWbibv6eyP+jabcGzP/Ng
AhdpMs8T9VyBodIeDTrA/jyxePfQoQ3y8Kk++1Y88lmq1Pwi43/gl6e4JSOK8Rhg
ORGs44WTLQFsxQBEnK2zttLpZ0NWMcxQotgYQV5MJtmBIIAMZkkI/2plyKoHteeW
+V0c0Ci0xcnz8qEHGBHqF2ma9n8Nmn/CEa+wWyvGWcBKqhQYkfjFKyMm8X5qFI5U
/xZ4SvGj0qoGWwYobCoNrYwmNlDKmIXzg73+lJ0L1EcnAj5zCBLJ7V44Ppz187bc
Vuid/gGgYzhoZwOKRVGuYc7HvqjtNerOb6z3mM4P6pwkED3XHOMQg/5Gql+aHzw=
=re6g
-----END PGP SIGNATURE-----


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]