public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mikael at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/60191] test case gfortran.dg/dynamic_dispatch_1/3.f03 fail on ARMv7
Date: Mon, 31 Mar 2014 09:14:00 -0000	[thread overview]
Message-ID: <bug-60191-4-3mQq8Q3rgO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60191-4@http.gcc.gnu.org/bugzilla/>

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

Mikael Morin <mikael at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mikael at gcc dot gnu.org

--- Comment #13 from Mikael Morin <mikael at gcc dot gnu.org> ---
Patch posted at
http://gcc.gnu.org/ml/gcc-patches/2014-03/msg01690.html

I have no time to review it now, so I'm just adding a cross-reference to
where the error_mark_node thing comes from:
It comes from http://gcc.gnu.org/r195890 or namely pr54107.


  parent reply	other threads:[~2014-03-31  9:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-14  8:39 [Bug fortran/60191] New: " bernd.edlinger at hotmail dot de
2014-02-14  8:42 ` [Bug fortran/60191] " pinskia at gcc dot gnu.org
2014-02-15 17:00 ` janus at gcc dot gnu.org
2014-02-16 10:03 ` bernd.edlinger at hotmail dot de
2014-02-16 10:47 ` dominiq at lps dot ens.fr
2014-02-16 11:53 ` janus at gcc dot gnu.org
2014-02-16 12:28 ` bernd.edlinger at hotmail dot de
2014-02-17  7:55 ` bernd.edlinger at hotmail dot de
2014-02-17  8:17 ` bernd.edlinger at hotmail dot de
2014-03-25 12:17 ` burnus at gcc dot gnu.org
2014-03-25 14:48 ` bernd.edlinger at hotmail dot de
2014-03-31  9:14 ` mikael at gcc dot gnu.org [this message]
2014-04-04 13:55 ` edlinger at gcc dot gnu.org
2014-04-05  6:13 ` bernd.edlinger at hotmail dot de
2014-04-10 20:14 ` edlinger 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-60191-4-3mQq8Q3rgO@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).