public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tkoenig at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/48890] [F95] Wrong length of a character component of named constant derived-type
Date: Mon, 04 May 2015 09:48:00 -0000 [thread overview]
Message-ID: <bug-48890-4-xXLje91bj6@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48890-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=48890
Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |tkoenig at gcc dot gnu.org
--- Comment #5 from Thomas Koenig <tkoenig at gcc dot gnu.org> ---
(In reply to Tobias Burnus from comment #4)
> (In reply to Francois-Xavier Coudert from comment #3)
> > It's a "Fortran 95"-only issue! See the variant below:
>
> Why? I don't see ad hoc anything which makes this a F95-only bug. It looks
> to me like a general (g)Fortran bug (F90, F95, F2003, F2008, F2018).
This means that this is a bug that is exposed by using only F95 features.
These should receive high priority because we can not yet claim
conformance to a standard > F95.
prev parent reply other threads:[~2015-05-04 9:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-05 20:00 [Bug fortran/48890] New: length of a character derived-type component mhp77 at gmx dot at
2013-02-26 16:04 ` [Bug fortran/48890] " dominiq at lps dot ens.fr
2015-05-03 21:35 ` [Bug fortran/48890] [F95] Wrong length of a character component of named constant derived-type fxcoudert at gcc dot gnu.org
2015-05-04 8:24 ` burnus at gcc dot gnu.org
2015-05-04 9:48 ` tkoenig at gcc dot gnu.org [this message]
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-48890-4-xXLje91bj6@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).