public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Douglas Rupp <rupp@gnat.com>
Cc: Richard Henderson <rth@redhat.com>,
	gcc-patches@gcc.gnu.org,        java-patches@gcc.gnu.org,
	libstdc++@gcc.gnu.org,
	       "Joseph S. Myers" <joseph@codesourcery.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: Mon, 05 Mar 2012 17:54:00 -0000	[thread overview]
Message-ID: <ydd7gyzrl0h.fsf@manam.CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <4F54FAB6.7060101@gnat.com> (Douglas Rupp's message of "Mon, 05	Mar 2012 09:41:10 -0800")

Douglas Rupp <rupp@gnat.com> writes:

> On 3/5/2012 9:28 AM, Richard Henderson wrote:
>> On 03/05/2012 09:14 AM, Rainer Orth wrote:
>>> * In the alpha backend, there are a couple of cases that might be
>>>    osf-specific, but I cannot tell for certain:
>>>
>>>    macro				  osf5.h        alpha.h
>>>
>>>    TARGET_AS_CAN_SUBTRACT_LABELS	  1		TARGET_GAS
>>>
>>>    I cannot tell if !TARGET_GAS configurations exist, especially Alpha VMS.
>>>    Also, in alpha.h there are some references to mips-tfile, which is
>>>    gone with osf.  If there are no non-gas configrations remaining, that
>>>    stuff can go, too.
>> Given that GAS supports VMS, I suspect that all targets are now GAS.
>> I'll let the adacore folks answer that for certain howeverl.
>>
> All Alpha/VMS targets use GAS.

Fine.  Given that the BSDs have no option but to use gas (and all of
them include MASK_GAS in config.gcc (target_cpu_default), the
!TARGET_GAS support can go.

I'll either do this in a followup patch or leave it to the alpha
maintainers.

	Rainer

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

  reply	other threads:[~2012-03-05 17:54 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 [this message]
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
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=ydd7gyzrl0h.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 \
    --cc=rupp@gnat.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).