public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "alex_y_xu at yahoo dot ca" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug dynamic-link/28453] ld.so segfaults when relocating x86 libstdc++.so compiled with -fno-plt
Date: Thu, 09 Dec 2021 17:47:28 +0000 [thread overview]
Message-ID: <bug-28453-131-rF78MZkbrg@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-28453-131@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=28453
--- Comment #10 from alex_y_xu at yahoo dot ca ---
Reproduction instructions from scratch:
0. Install gcc 11.2.0 (unsure if Gentoo patches have an effect) on x86_64.
1. Download and extract gcc 11.2.0 (without any patches).
2. export CFLAGS='-O2 -fno-align-jumps -fno-align-functions -fno-align-loops
-fno-align-labels -fgcse-after-reload -floop-interchange -fpeel-loops
-fpredictive-commoning -ftree-loop-vectorize -ftree-partial-pre
-ftree-slp-vectorize -fgraphite-identity -floop-nest-optimize
-fdevirtualize-at-ltrans -fno-semantic-interposition -march=native -fno-plt
-mtls-dialect=gnu2 -pipe'; export CXXFLAGS="$CFLAGS" LDFLAGS='-Wl,--sort-common
-Wl,-O1 -Wl,--as-needed -Wl,-z,relro -Wl,-z,now'; ./configure
--disable-bootstrap --enable-lto && make all-target-libstdc++-v3
3. Examine file
./x86_64-pc-linux-gnu/32/libstdc++-v3/src/.libs/libstdc++.so.6.0.29.
I cannot attach the dependencies as it exceeds the file size limit, even after
excluding libc and compressing with xz -9e.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-09 17:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 0:45 [Bug dynamic-link/28453] New: " alex_y_xu at yahoo dot ca
2021-10-25 1:23 ` [Bug dynamic-link/28453] " sam at gentoo dot org
2021-11-17 8:43 ` fweimer at redhat dot com
2021-11-17 13:09 ` hjl.tools at gmail dot com
2021-11-17 13:31 ` alex_y_xu at yahoo dot ca
2021-11-17 14:10 ` hjl.tools at gmail dot com
2021-11-17 14:17 ` fweimer at redhat dot com
2021-11-17 14:39 ` alex_y_xu at yahoo dot ca
2021-11-17 14:58 ` hjl.tools at gmail dot com
2021-11-17 14:59 ` hjl.tools at gmail dot com
2021-11-17 16:05 ` hjl.tools at gmail dot com
2021-12-09 17:47 ` alex_y_xu at yahoo dot ca [this message]
2021-12-09 17:51 ` alex_y_xu at yahoo dot ca
2021-12-10 2:32 ` hjl.tools at gmail dot com
2021-12-10 16:02 ` alex_y_xu at yahoo dot ca
2021-12-10 19:55 ` hjl.tools at gmail dot com
2021-12-28 17:32 ` alex_y_xu at yahoo dot ca
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-28453-131-rF78MZkbrg@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).