public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sebpop at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/38262] [4.4 regression] GCC components unnecessarily link with shared gmp/mpfr
Date: Wed, 26 Nov 2008 18:21:00 -0000 [thread overview]
Message-ID: <20081126182001.4794.qmail@sourceware.org> (raw)
In-Reply-To: <bug-38262-578@http.gcc.gnu.org/bugzilla/>
------- Comment #3 from sebpop at gmail dot com 2008-11-26 18:20 -------
Subject: Re: [4.4 regression] GCC components unnecessarily link with shared
gmp/mpfr
Thanks for catching the missing parts.
Here is the updated patch. Does this patch look correct?
I sent this patch to test on the gccfarm and will send an email to
gcc-patches after it completes regstrap.
Thanks,
Sebastian
On Tue, Nov 25, 2008 at 5:08 PM, ghazi at gcc dot gnu dot org
<gcc-bugzilla@gcc.gnu.org> wrote:
>
>
> ------- Comment #2 from ghazi at gcc dot gnu dot org 2008-11-25 23:08 -------
> (In reply to comment #1)
>> Subject: Re: New: [4.4 regression] GCC components unnecessarily link with
>> shared gmp/mpfr
>> Here is a patch from Dwarak for fixing this.
>> He will send this to review on gcc-patches@ list.
>> Sebastian Pop
>> --
>> AMD - GNU Tools
>
> Thanks, however I don't understand why in this patch xgcc and cpp are being
> linked with BACKENDLIBS. They don't linked with libbackend.a.
>
> Also, there are many more places where you do need to add BACKENDLIBS like
> cc1plus, cc1obj, f951, jc1, etc. See here for all the places you'll need to
> catch:
>
> http://gcc.gnu.org/ml/gcc-patches/2008-02/msg00187.html
>
>
> --
>
> ghazi at gcc dot gnu dot org changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Status|UNCONFIRMED |NEW
> Ever Confirmed|0 |1
> Last reconfirmed|0000-00-00 00:00:00 |2008-11-25 23:08:54
> date| |
>
>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38262
>
>
------- Comment #4 from sebpop at gmail dot com 2008-11-26 18:20 -------
Created an attachment (id=16780)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=16780&action=view)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38262
next prev parent reply other threads:[~2008-11-26 18:21 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 16:02 [Bug bootstrap/38262] New: " ghazi at gcc dot gnu dot org
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 [this message]
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=20081126182001.4794.qmail@sourceware.org \
--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: 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).