public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dominiq at lps dot ens dot fr" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/42353] [fortran-dev] Bogus Error: Name 'vtype$...' at (1) is an ambiguous reference ...
Date: Sun, 10 Jan 2010 13:34:00 -0000 [thread overview]
Message-ID: <20100110133357.32242.qmail@sourceware.org> (raw)
In-Reply-To: <bug-42353-6318@http.gcc.gnu.org/bugzilla/>
------- Comment #20 from dominiq at lps dot ens dot fr 2010-01-10 13:33 -------
> Regressions on fortran-dev branch fixed.
This caused pr42680 .
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42353
next prev parent reply other threads:[~2010-01-10 13:34 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-11 22:53 [Bug fortran/42353] New: [OOP] " anlauf at gmx dot de
2009-12-11 22:54 ` [Bug fortran/42353] " anlauf at gmx dot de
2009-12-11 23:13 ` janus at gcc dot gnu dot org
2009-12-13 21:10 ` janus at gcc dot gnu dot org
2009-12-13 21:41 ` janus at gcc dot gnu dot org
2009-12-16 21:16 ` anlauf at gmx dot de
2009-12-17 21:09 ` anlauf at gmx dot de
2009-12-28 14:15 ` janus at gcc dot gnu dot org
2009-12-28 14:29 ` janus at gcc dot gnu dot org
2009-12-28 15:24 ` janus at gcc dot gnu dot org
2009-12-28 18:35 ` anlauf at gmx dot de
2009-12-28 19:13 ` janus at gcc dot gnu dot org
2009-12-28 21:44 ` anlauf at gmx dot de
2009-12-28 21:59 ` janus at gcc dot gnu dot org
2009-12-28 22:39 ` anlauf at gmx dot de
2009-12-28 23:13 ` janus at gcc dot gnu dot org
2009-12-28 23:16 ` janus at gcc dot gnu dot org
2009-12-30 17:35 ` [Bug fortran/42353] [fortran-dev] " janus at gcc dot gnu dot org
2010-01-09 23:11 ` jvdelisle at gcc dot gnu dot org
2010-01-09 23:21 ` dominiq at lps dot ens dot fr
2010-01-10 13:34 ` dominiq at lps dot ens dot fr [this message]
2010-01-18 22:18 ` anlauf at gmx dot de
2010-01-19 0:25 ` jvdelisle at gcc dot gnu dot org
2010-01-19 2:37 ` jvdelisle at gcc dot gnu dot org
2010-01-22 4:31 ` jvdelisle at gcc dot gnu dot org
2010-01-22 4:32 ` jvdelisle at gcc dot gnu dot org
2010-04-16 5:59 ` pault at gcc dot gnu dot org
2010-04-18 13:13 ` janus at gcc dot gnu dot org
2010-04-18 13:50 ` pault at gcc dot gnu dot org
2010-04-18 13:55 ` dominiq at lps dot ens dot fr
2010-04-18 17:24 ` pault at gcc dot gnu dot org
2010-04-18 17:26 ` pault at gcc dot gnu dot org
2010-04-18 17:29 ` pault at gcc dot gnu dot org
2010-04-18 17:29 ` pault at gcc dot gnu dot org
2010-04-29 19:12 ` pault at gcc dot gnu dot 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=20100110133357.32242.qmail@sourceware.org \
--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).