public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Paolo Bonzini <bonzini@gnu.org>
Cc: gcc-patches@gcc.gnu.org,
	"Joseph S. Myers" <joseph@codesourcery.com>,
	       Ralf Wildenhues <Ralf.Wildenhues@gmx.de>,
	       Ian Lance Taylor <iant@google.com>,
	Steve Ellcey <sje@cup.hp.com>,
	       Richard Earnshaw <richard.earnshaw@arm.com>,
	       Ramana Radhakrishnan <ramana.radhakrishnan@arm.com>,
	       Nick Clifton <nickc@redhat.com>,
	Douglas Rupp <rupp@gnat.com>,
	       Tristan Gingold <gingold@adacore.com>,
	       Mike Stump <mikestump@comcast.net>,
	Kaz Kojima <kkojima@gcc.gnu.org>,
	       David Edelsohn <dje.gcc@gmail.com>,
	       Sterling Augustine <augustine.sterling@gmail.com>,
	       Arnaud Charlet <charlet@adacore.com>,
	java-patches@gcc.gnu.org,
	       Nicola Pero <nicola.pero@meta-innovation.com>,
	libstdc++@gcc.gnu.org,
	       Richard Sandiford <rdsandiford@googlemail.com>
Subject: Re: [build] Move unwinder to toplevel libgcc (v2)
Date: Fri, 05 Aug 2011 11:46:00 -0000	[thread overview]
Message-ID: <yddr550t71x.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4E3BBB39.7060608@gnu.org> (Paolo Bonzini's message of "Fri, 05	Aug 2011 11:43:21 +0200")

Paolo Bonzini <bonzini@gnu.org> writes:

>> How should we proceed with this patch, especially given the quite
>> moderate comments from most affected target maintainers?
>
> ARM is the only target we should care a bit about.  Any chance you can try
> cross-compiling it (with a combined tree it should not be hard)? Just to
> see that it builds.

I've tried to setup crosstool-NG in the past, but failed and haven't
gotten around to debugging this yet.  I still mean to, especially given
that I need to investigate testsuite issues in a cross environment.

Nick already ok'ed the arm (and frv) parts, so we should be ok for now.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

  parent reply	other threads:[~2011-08-05 11:46 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 13:33 Rainer Orth
2011-08-03 16:07 ` Nick Clifton
2011-08-03 21:11 ` Benjamin Kosnik
2011-08-05  9:43 ` Paolo Bonzini
2011-08-05  9:48   ` Andrew Haley
2011-08-05 11:46   ` Rainer Orth [this message]
2011-08-05 12:52     ` Andrew Haley
2011-08-05 13:33     ` Paolo Bonzini
     [not found] ` <201108052018.38537.mikael.morin@sfr.fr>
2011-08-05 19:49   ` Paolo Bonzini
     [not found]     ` <201108061243.19056.mikael.morin@sfr.fr>
2011-08-06 14:32       ` Paolo Bonzini
2011-08-10 13:47 ` Joseph S. Myers
2011-08-10 13:51   ` Rainer Orth
2011-08-10 13:57     ` Joseph S. Myers
2011-08-10 15:11       ` Rainer Orth
2011-08-10 16:05         ` Paolo Bonzini
2011-08-10 16:10           ` Rainer Orth
2011-08-10 17:00             ` Paolo Bonzini
2011-08-11 15:26               ` Rainer Orth
     [not found]                 ` <CAMe9rOrznkTrvxg-KC4TrNF5uSua654p_1R0GZ-9rkNUF5Z76A@mail.gmail.com>
2011-08-12  7:28                   ` Paolo Bonzini
     [not found]             ` <201108101750.43530.pedro@codesourcery.com>
2011-08-11 12:06               ` Paolo Bonzini
2011-08-11 14:25                 ` Rainer Orth
2011-08-11 14:38                   ` Joseph S. Myers
2011-08-11 14:42                     ` Paolo Bonzini
2011-08-11 15:23                       ` Joseph S. Myers
2011-08-11 15:32                         ` Rainer Orth
2011-08-11 16:18                           ` Paolo Bonzini
2011-08-11 19:53                             ` Rainer Orth
2011-08-11 14:44                     ` 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=yddr550t71x.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=Ralf.Wildenhues@gmx.de \
    --cc=augustine.sterling@gmail.com \
    --cc=bonzini@gnu.org \
    --cc=charlet@adacore.com \
    --cc=dje.gcc@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gingold@adacore.com \
    --cc=iant@google.com \
    --cc=java-patches@gcc.gnu.org \
    --cc=joseph@codesourcery.com \
    --cc=kkojima@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mikestump@comcast.net \
    --cc=nickc@redhat.com \
    --cc=nicola.pero@meta-innovation.com \
    --cc=ramana.radhakrishnan@arm.com \
    --cc=rdsandiford@googlemail.com \
    --cc=richard.earnshaw@arm.com \
    --cc=rupp@gnat.com \
    --cc=sje@cup.hp.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).