public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Kumba <kumba@gentoo.org>
To: David Daney <ddaney@avtrex.com>
Cc: gcc-patches@gcc.gnu.org, mips@gentoo.org,
	rdsandiford@googlemail.com,   GCC Mailing List <gcc@gcc.gnu.org>
Subject: Re: [PATCH]: GCC Scheduler support for R10000 on MIPS
Date: Tue, 19 Aug 2008 02:59:00 -0000	[thread overview]
Message-ID: <48AA1F61.3040102@gentoo.org> (raw)
In-Reply-To: <48A9A3EB.9020703@avtrex.com>

David Daney wrote:

> Yes there is.  I'm not sure if Richard can cause them to be sent to you, 
> but certainly requesting copyright assignment documents on 
> gcc@gcc.gnu.org would work.  It can often take many weeks to get them 
> processed, so starting as soon as possible would be a good idea.

I'll submit a request outside of this thread later on then.  Thanks for the info!

As far as processing time goes, will that impact getting this patch committed? 
My understanding is end of August for new features for gcc-4.4.


> It would depend on if any of the original patch code remains.  If so, 
> probably a copyright assignment for the original author would be 
> required as well (at least that is my understanding).

That's an interesting thought then.  I largely left his code intact while I used 
this patch throughout gcc-3.2, 3.3, and 3.4 (I simply updated it to apply to the 
subsequent releases in the 3.x series).  I only converted it to DFA in gcc-4.0, 
which was largely a complete rewrite, using the original patch as a guide to 
learn how DFA changed things around.  Plus, the core information comes from the 
Vr10000 manual anyways, available off www.necel.com.  Considering the very 
original patch was posted once to gcc-patches years ago for gcc-3.0 
consideration, I would be surprised if the e-mail address of that submission 
still goes to him.

Thoughts?

-- 
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org

"The past tempts us, the present confuses us, the future frightens us.  And our 
lives slip away, moment by moment, lost in that vast, terrible in-between."

--Emperor Turhan, Centauri Republic

  reply	other threads:[~2008-08-19  1:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01  1:53 Kumba
2008-08-02  4:29 ` Kumba
2008-08-02  9:48 ` Richard Sandiford
2008-08-03  3:37   ` Kumba
2008-08-03  7:20     ` Ralf Wildenhues
2008-08-03 10:40     ` Richard Sandiford
2008-08-04  7:20       ` Kumba
2008-08-04 19:23         ` Richard Sandiford
2008-08-04 19:30           ` contribute.html: compare pre/post patch testresults (was: [PATCH]: GCC Scheduler support for R10000 on MIPS) Ralf Wildenhues
2008-08-06 14:51             ` Ian Lance Taylor
2008-08-05  2:48           ` [PATCH]: GCC Scheduler support for R10000 on MIPS Kumba
2008-08-05 18:29             ` Richard Sandiford
2008-08-06  7:58               ` Kumba
2008-08-07 21:24                 ` Richard Sandiford
2008-08-08  8:46                   ` Kumba
2008-08-09  9:01                     ` Richard Sandiford
2008-08-13  8:53                       ` Kumba
2008-08-16 10:10                         ` Richard Sandiford
2008-08-18  8:51                           ` Kumba
2008-08-18 17:00                             ` David Daney
2008-08-19  2:59                               ` Kumba [this message]
2008-10-06 21:33                             ` Richard Sandiford

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=48AA1F61.3040102@gentoo.org \
    --to=kumba@gentoo.org \
    --cc=ddaney@avtrex.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=mips@gentoo.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).