public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Jeffrey A Law <law@cygnus.com>
To: Nick Clifton <nickc@cygnus.com>
Cc: jvickers@dial.pipex.com, gavin@cygnus.com,
	ulfc@calypso.engr.sgi.com, gcc-patches@gcc.gnu.org,
	binutils@sourceware.cygnus.com
Subject: Re: RFA: command line switches for QED series of MIPS processors.
Date: Wed, 21 Jun 2000 13:04:00 -0000	[thread overview]
Message-ID: <11701.961617104@upchuck> (raw)
In-Reply-To: <200006172152.OAA28095@elmo.cygnus.com>

  In message < 200006172152.OAA28095@elmo.cygnus.com >you write:
  > : Since you only add QED CPUs, and not e.g. (NEC) VR5432, VR5264
  > : or (IDT) RC64574, RC64575, it looks - in itself - like a marketing
  > : exercise commisioned by QED.
  > 
  > This is probably correct.  All I know is that as part of a contract
  > with QED we (Cygnus/Red Hat) were asked to add these command line
  > switches and to contribute them back to the net community.
QED wants their users to be able to supply flags for the QED chips and
has paid Cygnus/Red Hat to make such options available to QED.

We agreed to contribute those changes to the official tree; however, if the
changes are rejected by the community, then they will not go into the
official sources.

  > There may be more optimisations to follow, but if so, I am not
  > scheduled to do the work, so I do not know what might be involved.
I have no idea.

jeff

  reply	other threads:[~2000-06-21 13:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-17 14:52 Nick Clifton
2000-06-21 13:04 ` Jeffrey A Law [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-15 12:12 Nick Clifton
2000-06-17 14:02 ` John Vickers
2000-06-21 13:05   ` Jeffrey A Law

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=11701.961617104@upchuck \
    --to=law@cygnus.com \
    --cc=binutils@sourceware.cygnus.com \
    --cc=gavin@cygnus.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jvickers@dial.pipex.com \
    --cc=nickc@cygnus.com \
    --cc=ulfc@calypso.engr.sgi.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).