public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60576] [4.8/4.9 Regression] FAIL: gfortran.dg/assumed_rank_7.f90
Date: Wed, 26 Mar 2014 21:05:00 -0000	[thread overview]
Message-ID: <bug-60576-4-aes3nMDWkP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60576-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #6 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
H.J. just filed a separate PR about the ichar_3.f90 failure in PR60678.


  parent reply	other threads:[~2014-03-26 21:05 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-18 23:02 [Bug fortran/60576] New: [4.9 " hjl.tools at gmail dot com
2014-03-19  9:54 ` [Bug fortran/60576] " jakub at gcc dot gnu.org
2014-03-19  9:56 ` rguenth at gcc dot gnu.org
2014-03-19 10:03 ` jakub at gcc dot gnu.org
2014-03-19 15:29 ` [Bug fortran/60576] [4.8/4.9 " jakub at gcc dot gnu.org
2014-03-21 20:42 ` dominiq at lps dot ens.fr
2014-03-24 18:08 ` jakub at gcc dot gnu.org
2014-03-24 20:38 ` mikael at gcc dot gnu.org
2014-03-26 21:05 ` jakub at gcc dot gnu.org [this message]
2014-03-28 13:05 ` burnus at gcc dot gnu.org
2014-03-28 20:31 ` [Bug fortran/60576] [4.8 " jakub at gcc dot gnu.org
2014-03-28 20:35 ` burnus at gcc dot gnu.org
2014-03-28 20:57 ` burnus at gcc dot gnu.org
2014-03-28 20:58 ` burnus at gcc dot gnu.org
2014-03-28 21:19 ` hjl.tools at gmail dot com
2014-03-28 21:24 ` burnus at gcc dot gnu.org
2014-03-28 21:39 ` dominiq at lps dot ens.fr
2014-03-29 17:08 ` dominiq at lps dot ens.fr
2014-03-30  9:33 ` mikael at gcc dot gnu.org
2014-05-22  9:07 ` rguenth at gcc dot gnu.org
2014-12-10 12:54 ` rguenth at gcc dot gnu.org
2014-12-10 17:44 ` [Bug fortran/60576] [4.8/4.9/5 " dominiq at lps dot ens.fr
2014-12-19 13:26 ` jakub at gcc dot gnu.org
2015-06-23  8:19 ` [Bug fortran/60576] [4.8/4.9/5/6 " rguenth at gcc dot gnu.org
2015-06-26 19:55 ` [Bug fortran/60576] [4.9/5/6 " jakub at gcc dot gnu.org
2015-06-26 20:27 ` jakub at gcc dot gnu.org
2021-01-07 22:25 ` [Bug fortran/60576] [8/9/10/11 " anlauf at gcc dot gnu.org
2021-05-14  9:47 ` [Bug fortran/60576] [9/10/11/12 " jakub at gcc dot gnu.org
2021-05-31 17:32 ` dominiq at lps dot ens.fr
2021-06-01  8:06 ` rguenth at gcc dot gnu.org
2022-05-27  9:35 ` [Bug fortran/60576] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:30 ` jakub at gcc dot gnu.org
2023-07-07 10:30 ` [Bug fortran/60576] [11/12/13/14 " rguenth 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-60576-4-aes3nMDWkP@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).