public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "burnus at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/37203] New: Check ORDER= of RESHAPE
Date: Fri, 22 Aug 2008 17:44:00 -0000 [thread overview]
Message-ID: <bug-37203-13404@http.gcc.gnu.org/bugzilla/> (raw)
Found at
http://groups.google.com/group/gg95/browse_thread/thread/d27f173506fbb9cc
The following program compiles without any warning, but NAG f95 prints:
Error: line 6: Value 2 in ORDER arg to RESHAPE duplicated
integer, dimension(6) :: source1 = (/ 1, 2, 3, 4, 5, 6 /)
integer, dimension(2) :: shape1 = (/ 2, 5/)
integer, dimension(2) :: pad1 = (/ 0, 0/)
write (unit=*,fmt=*) reshape(source1, shape1, pad1, (/2,1/)) ! Valid
write (unit=*,fmt=*) reshape(source1, shape1, pad1, (/2,2/)) ! Invalid
end
--
Summary: Check ORDER= of RESHAPE
Product: gcc
Version: 4.4.0
Status: UNCONFIRMED
Keywords: diagnostic
Severity: normal
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: burnus at gcc dot gnu dot org
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37203
next reply other threads:[~2008-08-22 17:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 17:44 burnus at gcc dot gnu dot org [this message]
2008-08-23 14:13 ` [Bug fortran/37203] " tkoenig at gcc dot gnu dot org
2008-09-07 9:14 ` tkoenig at gcc dot gnu dot org
2008-09-07 13:36 ` tkoenig at gcc dot gnu dot org
2009-01-04 14:57 ` dfranke at gcc dot gnu dot org
2009-01-04 19:00 ` mikael at gcc dot gnu dot org
2009-01-04 19:10 ` dfranke at gcc dot gnu dot org
2009-01-04 21:25 ` dfranke at gcc dot gnu dot org
2009-03-22 12:12 ` dfranke at gcc dot gnu dot org
2009-06-04 21:53 ` burnus at gcc dot gnu dot org
2009-06-04 21:59 ` burnus at gcc dot gnu dot org
2009-06-06 21:10 ` burnus 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=bug-37203-13404@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).