From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc-patches@gcc.gnu.org
Cc: Paolo Bonzini <bonzini@gnu.org>, rdsandiford@googlemail.com
Subject: Re: [build] Move sync, mips16.S to toplevel libgcc
Date: Tue, 09 Aug 2011 12:32:00 -0000 [thread overview]
Message-ID: <yddd3gepys5.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87d3gipef7.fsf@firetop.home> (Richard Sandiford's message of "Sat, 06 Aug 2011 19:45:16 +0100")
Richard Sandiford <rdsandiford@googlemail.com> writes:
>> So this patch only deals with the sync functions proper and should be
>> relatively straightforward. Richard, could you please try this one,
>> too?
>
> Sure. Tested on mips64-linux-gnu, where it works fine, thanks.
Fine, thanks for testing.
>> 2011-07-10 Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
>>
>> gcc:
>> * config/sync.c: Move to ../libgcc.
>> * Makefile.in (libgcc.mvars): Remove LIBGCC_SYNC,
>> LIBGCC_SYNC_CFLAGS.
>> * config/mips/t-libgcc-mips16 (LIBGCC_SYNC, LIBGCC_SYNC_CFLAGS):
>> Remove.
>>
>> libgcc:
>> * sync.c: New file.
>> * config/mips/t-mips16: New file.
>> * config.host (mips64*-*-linux*): Add mips/t-mips16 to tmake_file.
>> (mips*-*-linux*): Likewise.
>> (mips*-sde-elf*): Likewise.
>> (mipsisa32-*-elf*): Join with mipsisa32r2-*-elf*,
>> mipsisa64-*-elf*, mipsisa64r2-*-elf*.
>> Add mips/t-mips16 to tmake_file.
>> (mipsisa64sb1-*-elf*): Add mips/t-mips16 to tmake_file.
>> (mips-*-elf*): Likewise.
>> (mips64-*-elf*): Likewise.
>> (mips64orion-*-elf*): Likewise.
>> (mips*-*-rtems*): Likewise.
>> (mipstx39-*-elf*): Likewise.
>> * Makefile.in: Use SYNC instead of LIBGCC_SYNC.
>> ($(libgcc-sync-size-funcs-o)): Use SYNC_CFLAGS instead of
>> LIBGCC_SYNC_CFLAGS.
>> Use $(srcdir) to refer to sync.c.
>> Use $<.
>> ($(libgcc-sync-funcs-o)): Likewise.
>> ($(libgcc-sync-size-funcs-s-o)): Likewise.
>> ($(libgcc-sync-funcs-s-o)): Likewise.
>
> OK for the MIPS parts.
Paolo, are you ok with the build parts?
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2011-08-09 12:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-12 16:35 Rainer Orth
2011-08-04 17:59 ` Rainer Orth
2011-08-06 19:27 ` Richard Sandiford
2011-08-09 12:32 ` Rainer Orth [this message]
2011-08-09 16:40 ` Paolo Bonzini
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=yddd3gepys5.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=bonzini@gnu.org \
--cc=gcc-patches@gcc.gnu.org \
--cc=rdsandiford@googlemail.com \
/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).