From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: "Joseph S. Myers" <joseph@codesourcery.com>
Cc: gcc-patches@gcc.gnu.org, java-patches@gcc.gnu.org,
libstdc++@gcc.gnu.org, Richard Henderson <rth@redhat.com>,
Bruce Korb <bkorb@gnu.org>,
Arnaud Charlet <charlet@adacore.com>,
Tristan Gingold <gingold@adacore.com>
Subject: Re: Remove obsolete Tru64 UNIX V5.1B support
Date: Tue, 06 Mar 2012 13:14:00 -0000 [thread overview]
Message-ID: <yddpqcprhvy.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <Pine.LNX.4.64.1203052310000.17538@digraph.polyomino.org.uk> (Joseph S. Myers's message of "Mon, 5 Mar 2012 23:13:10 +0000 (UTC)")
"Joseph S. Myers" <joseph@codesourcery.com> writes:
>> There's one particular issue: the change to java/io/File.java required
>> my to regenerate the .class file in classpath. I've used Sun javac
>> -target 1.5 for that and hope I got it right.
>
> I'd have expected regeneration to use GCJ built to use ECJ, though I don't
> know.
I've never tried this. Given that the .class file lives below
libjava/classpath and has to be synced with upstream Classpath anyway, I
hope the Java maintainers will take care of that.
At least with the javac-built File.class I had no libjava testsuite
failures.
>> * With the removal of #pragma extern_prefix support, gcc/po/gcc.pot
>> needs to be regenerated. Since I'm not positive I have the right
>> tools and trying found unrelated changes, I've omitted that change.
>
> There is no expectation that anyone changing diagnostics regenerates this
> file; it's regenerated as needed before submission to the Translation
> Project.
Ok, thanks.
>> gcc:
>> * config.gcc (alpha*-dec-osf5.1*): Remove.
>
> I'd suggest removing the extra_passes mechanism in the followup since this
> was the only user of that mechanism in config.gcc.
Yup, will do.
>> * target.def (handle_pragma_extern_prefix): Remove.
>
> Removed hooks should be poisoned in system.h.
Ok. Greping for current occurences obviously missed this :-)
Thanks.
Rainer
--
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University
next prev parent reply other threads:[~2012-03-06 13:14 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 17:14 Rainer Orth
2012-03-05 17:28 ` Richard Henderson
2012-03-05 17:36 ` Jakub Jelinek
2012-03-05 17:52 ` Rainer Orth
2012-03-05 17:41 ` Douglas Rupp
2012-03-05 17:54 ` Rainer Orth
2012-03-05 18:00 ` Rainer Orth
2012-03-06 8:39 ` Tristan Gingold
2012-03-05 17:32 ` Bruce Korb
2012-03-05 23:13 ` Joseph S. Myers
2012-03-06 13:14 ` Rainer Orth [this message]
2012-03-06 17:55 ` David Daney
2012-03-06 19:08 ` Andrew Haley
2012-03-07 14:36 ` Rainer Orth
2012-03-12 16:33 ` Rainer Orth
2012-03-06 8:57 ` Tristan Gingold
2012-03-06 13:24 ` Rainer Orth
2012-03-12 16:07 ` Rainer Orth
2012-03-12 16:19 ` Paolo Carlini
2012-03-12 16:23 ` Rainer Orth
-- strict thread matches above, loose matches on Subject: below --
2012-03-05 17:09 Rainer Orth
2012-03-05 17:20 ` Andrew Haley
2012-03-05 17:58 ` Jonathan Wakely
2012-03-06 13:12 ` Rainer Orth
2012-03-06 8:44 ` Arnaud Charlet
2012-03-06 13:19 ` 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=yddpqcprhvy.fsf@manam.CeBiTec.Uni-Bielefeld.DE \
--to=ro@cebitec.uni-bielefeld.de \
--cc=bkorb@gnu.org \
--cc=charlet@adacore.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gingold@adacore.com \
--cc=java-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
--cc=libstdc++@gcc.gnu.org \
--cc=rth@redhat.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).