public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ghazi at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/38262] New: [4.4 regression] GCC components unnecessarily link with shared gmp/mpfr Date: Tue, 25 Nov 2008 16:02:00 -0000 [thread overview] Message-ID: <bug-38262-578@http.gcc.gnu.org/bugzilla/> (raw) As noted here: http://gcc.gnu.org/ml/gcc/2008-11/msg00234.html various components of GCC (xgcc, gcov, etc) are linking unnecessarily with gmp/mpfr. I believe we only need to do that for executables linked against libbackend.a (like cc1). The result is exposed when gmp/mpfr are shared libraries and appear in the ldd output. This bug was previously fixed in PR35107 but regressed during the graphite merge. http://gcc.gnu.org/viewcvs/trunk/gcc/Makefile.in?r1=139854&r2=139893 -- Summary: [4.4 regression] GCC components unnecessarily link with shared gmp/mpfr Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ghazi at gcc dot gnu dot org BugsThisDependsOn: 35107 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38262
next reply other threads:[~2008-11-25 16:02 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-11-25 16:02 ghazi at gcc dot gnu dot org [this message] 2008-11-25 16:27 ` [Bug bootstrap/38262] " pinskia at gcc dot gnu dot org 2008-11-25 20:25 ` [Bug bootstrap/38262] New: " Sebastian Pop 2008-11-25 20:27 ` [Bug bootstrap/38262] " sebpop at gmail dot com 2008-11-25 23:10 ` ghazi at gcc dot gnu dot org 2008-11-26 18:19 ` Sebastian Pop 2008-11-26 18:21 ` sebpop at gmail dot com 2008-11-26 19:12 ` ghazi at gcc dot gnu dot org 2008-11-28 9:40 ` jakub at gcc dot gnu dot org 2008-12-05 6:34 ` Sebastian Pop 2008-12-05 6:35 ` sebpop at gmail dot com 2008-12-05 8:04 ` spop at gcc dot gnu dot org 2008-12-05 8:06 ` spop at gcc dot gnu dot org 2008-12-05 8:53 ` jakub at gcc dot gnu dot org
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-38262-578@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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).