public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sgk at troutmask dot apl.washington.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48426] [patch] Quad precision promotion
Date: Fri, 15 Apr 2011 17:00:00 -0000	[thread overview]
Message-ID: <bug-48426-4-9xHV8yJwVd@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48426-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48426

--- Comment #12 from Steve Kargl <sgk at troutmask dot apl.washington.edu> 2011-04-15 16:59:41 UTC ---
On Fri, Apr 15, 2011 at 04:41:06PM +0000, jvdelisle at gcc dot gnu.org wrote:
> Steve, I can clean this up but i am not clear on copyright assignment.  Any
> issues on this?

The patch touches several files and more than a few lines,
so I think it may exceed the threshold of a patch without
copyright assignment.  We should probably check with  
Andreas Kloeckner if he has an assignment on file. 

Note, the manual changes to add a warning is needed because
these options effective storage association, which has an impact
on EQUIVALENCE and COMMON and perhaps others.


  parent reply	other threads:[~2011-04-15 17:00 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-03 18:04 [Bug fortran/48426] New: " inform at tiker dot net
2011-04-03 18:05 ` [Bug fortran/48426] " inform at tiker dot net
2011-04-03 19:25 ` kargl at gcc dot gnu.org
2011-04-03 19:50 ` inform at tiker dot net
2011-04-03 21:14   ` Jerry DeLisle
2011-04-03 20:33 ` sgk at troutmask dot apl.washington.edu
2011-04-03 21:14 ` jvdelisle at frontier dot com
2011-04-05  2:12 ` inform at tiker dot net
2011-04-05  2:13 ` inform at tiker dot net
2011-04-15 14:57 ` inform at tiker dot net
2011-04-15 15:31 ` jvdelisle at gcc dot gnu.org
2011-04-15 16:12 ` sgk at troutmask dot apl.washington.edu
2011-04-15 16:43 ` jvdelisle at gcc dot gnu.org
2011-04-15 17:00 ` sgk at troutmask dot apl.washington.edu [this message]
2011-04-15 19:49 ` inform at tiker dot net
2011-04-15 20:32 ` jvdelisle at gcc dot gnu.org
2011-11-07 19:28 ` inform at tiker dot net
2011-11-07 20:04 ` sgk at troutmask dot apl.washington.edu
2011-11-10  0:37 ` inform at tiker dot net
2012-01-16 18:28 ` kargl at gcc dot gnu.org
2012-01-16 18:29 ` kargl at gcc dot gnu.org
2012-01-18 18:50 ` kargl at gcc dot gnu.org
2012-01-19  8:55 ` burnus at gcc dot gnu.org
2012-01-19 17:11 ` kargl at gcc dot gnu.org

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=bug-48426-4-9xHV8yJwVd@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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).