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 libfortran/67140] undefined reference to _gfortran_mvbits_i16
Date: Sat, 08 Aug 2015 18:08:00 -0000	[thread overview]
Message-ID: <bug-67140-4-N3iu7VJmTU@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-67140-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67140

--- Comment #4 from Steve Kargl <sgk at troutmask dot apl.washington.edu> ---
On Sat, Aug 08, 2015 at 05:50:03PM +0000, fxcoudert at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67140
> 
> Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>                  CC|                            |fxcoudert at gcc dot gnu.org
> 
> --- Comment #3 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
> (In reply to kargl from comment #2)
> > Patched built and tested with OP's code.
> > Regression test passed.
> 
> Patch approved for trunk, with the following testcase (just double-check that
> it passes!):
> 

Thanks! I'll take of this later today.


  parent reply	other threads:[~2015-08-08 18:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-67140-4@http.gcc.gnu.org/bugzilla/>
2015-08-07  0:40 ` kargl at gcc dot gnu.org
2015-08-08 18:08 ` sgk at troutmask dot apl.washington.edu [this message]
2015-08-10 17:42 ` kargl at gcc dot gnu.org
2015-08-10 17:50 ` kargl at gcc dot gnu.org
2015-08-10 21:24 ` hjl.tools at gmail dot com
2015-08-10 21:40 ` hjl.tools at gmail dot com
2015-08-10 21:42 ` sgk at troutmask dot apl.washington.edu
2015-08-10 21:45 ` kargl at gcc dot gnu.org
2015-08-10 21:45 ` kargl at gcc dot gnu.org
2015-08-11  7:40 ` fxcoudert 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-67140-4-N3iu7VJmTU@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).