public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <bonzini@gnu.org>
To: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
Cc: Bernd Schmidt <bernds@codesourcery.com>, gcc-patches@gcc.gnu.org
Subject: Re: Massive breakage with your libgcc patches
Date: Mon, 21 Nov 2011 16:46:00 -0000	[thread overview]
Message-ID: <4ECA7503.70407@gnu.org> (raw)
In-Reply-To: <yddk46txz05.fsf@manam.CeBiTec.Uni-Bielefeld.DE>

On 11/21/2011 04:43 PM, Rainer Orth wrote:
> Paolo Bonzini<bonzini@gnu.org>  writes:
>
>> On 11/07/2011 07:15 PM, Rainer Orth wrote:
>>> 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?
>>
>> Looks ok, but these look like they could also be broken.
>
> Sorry it took me so long, but this weekend I finally had a close look
> at both the explicit settings of LIB2ADD and LIB2FUNCS_EXCLUDE.  The
> latter are unproblematic since the files affected are disjunct.  For
> LIB2ADD, here are the problematic cases.  All others explicitly setting
> LIB2ADD have no issues since there are no t-* fragments setting LIB2ADD
> before.
>
> i386/t-darwin64:LIB2ADD = $(srcdir)/config/darwin-64.c
>
>    The file is currently unused, was lost in the migration for
>    x86_64-*-darwin*.  The same settings are already in i386/t-darwin, so
>    the file is superfluous and can be removed.
>
> iq2000/t-iq2000:LIB2ADD = $(srcdir)/udivmod.c \
>
>    This file is unused, now restored, otherwise no problem.
>
> pa/t-pa64:LIB2ADD = $(srcdir)/config/pa/quadlib.c
>
>    This overrides pa/t-hpux, originally we had pa/t-pa64 pa/t-pa-hpux
>    without overrides, but the result is ok.
>
> rs6000/t-darwin64:LIB2ADD = $(srcdir)/config/rs6000/darwin-tramp.S \
>
>    Overrides rs6000/t-darwin, as it did before the move.
>
> rs6000/t-lynx:LIB2ADD = $(srcdir)/config/rs6000/tramp.S
>
>    This file is currently unused, but necessary.  t-lynx is also missing,
>    but no settings left.
>
> rs6000/t-netbsd:LIB2ADD = $(srcdir)/config/rs6000/tramp.S
>
>    unused, necessary
>
> sh/t-netbsd:LIB2ADD =
>
>    The override poses no problem, but is unnecessary since nothing sets
>    LIB2ADD before.
>
> t-vxworks:LIB2ADD = $(srcdir)/config/vxlib.c $(srcdir)/config/vxlib-tls.c
>
>    Ok, but missing from powerpc-wrs-vxworks which didn't add to tmake_file.
>
> The following patch implements those observations.
>
> Ok for mainline?
>
> 	Rainer
>
>
> 2011-11-20  Rainer Orth<ro@CeBiTec.Uni-Bielefeld.DE>
>
> 	libgcc:
> 	* config.host (iq2000*-*-elf*): Add iq2000/t-iq2000 to tmake_file.
> 	(powerpc-*-netbsd*): Add rs6000/t-netbsd to tmake_file.
> 	(powerpc-wrs-vxworks, powerpc-wrs-vxworksae): Add to tmake_file.
> 	(powerpc-*-lynxos*): Add rs6000/t-lynx to tmake_file.
> 	* config/i386/t-darwin64: Remove.
> 	* config/sh/t-netbsd (LIB2ADD): Remove.
>
>
>
>
>
>

Ok.

Paolo

  reply	other threads:[~2011-11-21 15:58 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
2011-11-08 13:27                         ` Paolo Bonzini
2011-11-21 16:41                           ` Rainer Orth
2011-11-21 16:46                             ` Paolo Bonzini [this message]
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=4ECA7503.70407@gnu.org \
    --to=bonzini@gnu.org \
    --cc=bernds@codesourcery.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=ro@CeBiTec.Uni-Bielefeld.DE \
    /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).