From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Bernd Schmidt <bernds@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, bonzini@gnu.org
Subject: Re: Massive breakage with your libgcc patches
Date: Mon, 07 Nov 2011 18:38:00 -0000 [thread overview]
Message-ID: <yddhb2fx0h3.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4EB7D942.6080600@codesourcery.com> (Bernd Schmidt's message of "Mon, 07 Nov 2011 14:12:34 +0100")
[-- Attachment #1: Type: text/plain, Size: 746 bytes --]
Bernd Schmidt <bernds@codesourcery.com> writes:
> On 11/03/11 20:20, Rainer Orth wrote:
>>
>> * config/c6x/t-elf (LIB2ADDEH): Set.
>> * config/c6x/t-c6x-elf: Remove.
>
> It builds now, but parts of libgcc are missing. There's no sign of
> muldf3, for examples.
I found the problem: before, LIB2ADD was passed in from gcc/config via
libgcc.mvars, and added to in t-softfp. Now the order of the t-*
fragments has been kept the same, with the assignment to LIB2ADD in
c6x/t-elf overriding what has been constructed by t-softfp before.
The following patch did the trick for me, could you give it a try?
Thanks.
Rainer
2011-11-07 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
* config/c6x/t-elf (LIB2ADD): Add instead of assigning.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: c6x-softfp.patch --]
[-- Type: text/x-patch, Size: 456 bytes --]
diff --git a/libgcc/config/c6x/t-elf b/libgcc/config/c6x/t-elf
--- a/libgcc/config/c6x/t-elf
+++ b/libgcc/config/c6x/t-elf
@@ -8,7 +8,7 @@ LIB1ASMFUNCS += _push_rts _pop_rts _call
LIB2FUNCS_EXCLUDE = _cmpdi2 _ucmpdi2 _gcc_bcmp _eprintf _clzsi _clzdi
-LIB2ADD = $(srcdir)/config/c6x/gef.c \
+LIB2ADD += $(srcdir)/config/c6x/gef.c \
$(srcdir)/config/c6x/gtf.c \
$(srcdir)/config/c6x/lef.c \
$(srcdir)/config/c6x/ltf.c \
[-- Attachment #3: Type: text/plain, Size: 144 bytes --]
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-11-07 18:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-15 17:53 CFT: [build] Move crtstuff support to toplevel libgcc Rainer Orth
2011-08-15 21:00 ` Hans-Peter Nilsson
2011-08-16 17:13 ` Rainer Orth
2011-11-02 12:49 ` Rainer Orth
2011-11-02 20:16 ` Massive breakage with your libgcc patches Hans-Peter Nilsson
2011-11-02 20:26 ` Bernd Schmidt
2011-11-03 13:17 ` Rainer Orth
2011-11-03 13:58 ` Bernd Schmidt
2011-11-03 17:28 ` Rainer Orth
2011-11-03 17:54 ` Bernd Schmidt
2011-11-03 18:15 ` Rainer Orth
2011-11-03 18:48 ` Bernd Schmidt
2011-11-03 19:31 ` Rainer Orth
2011-11-04 12:01 ` Bernd Schmidt
2011-11-07 13:46 ` Bernd Schmidt
2011-11-07 18:38 ` Rainer Orth [this message]
2011-11-08 13:27 ` Paolo Bonzini
2011-11-21 16:41 ` Rainer Orth
2011-11-21 16:46 ` Paolo Bonzini
2011-11-08 16:56 ` Bernd Schmidt
2011-11-08 18:02 ` Rainer Orth
2011-11-29 16:22 ` Bernd Schmidt
2011-11-29 16:28 ` Paolo Bonzini
2011-11-03 13:14 ` Rainer Orth
2011-11-03 14:46 ` Hans-Peter Nilsson
2011-11-03 15:42 ` Hans-Peter Nilsson
2011-11-03 15:42 ` Rainer Orth
2011-11-02 21:29 ` CFT: [build] Move crtstuff support to toplevel libgcc Jason Merrill
2011-11-02 21:47 ` Jason Merrill
2011-11-03 13:07 ` Rainer Orth
2011-11-03 13:12 ` Paolo Bonzini
2011-11-03 16:09 ` Jason Merrill
2011-11-03 11:01 ` Andreas Schwab
2011-11-03 11:37 ` Matthew Gretton-Dann
2011-11-03 16:42 ` Rainer Orth
2011-11-04 13:43 ` Andreas Krebbel
2011-11-04 14:34 ` Rainer Orth
2011-11-04 14:38 ` Andreas Krebbel
2011-11-04 14:54 ` Rainer Orth
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=yddhb2fx0h3.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=bernds@codesourcery.com \
--cc=bonzini@gnu.org \
--cc=gcc-patches@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).