public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pbrook at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/16898] New: Aliasing problem with array descriptors
Date: Fri, 06 Aug 2004 14:32:00 -0000 [thread overview]
Message-ID: <20040806143250.16898.pbrook@gcc.gnu.org> (raw)
Following code compiled with gfortran -O2 -mtune=i686
Could be a frontend bug not setting alias sets properly. When foo is inlined,
a=>NULL is then scheduled after the body of foo.
Based on gfortran.dg/ret_pointer_1.f90
program aliasing_borken
integer, pointer, dimension(:) :: a
integer, target, dimension(2) :: b
a => NULL()
call foo(a);
if (.not. associated (a, b)) call abort
contains
subroutine foo(r)
integer, pointer, dimension(:) :: r
r => b
end subroutine
end program
--
Summary: Aliasing problem with array descriptors
Product: gcc
Version: 3.5.0
Status: UNCONFIRMED
Keywords: wrong-code
Severity: normal
Priority: P2
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: pbrook at gcc dot gnu dot org
CC: gcc-bugs at gcc dot gnu dot org
GCC build triplet: i686-pc-linux-gnu
GCC host triplet: i686-pc-linux-gnu
GCC target triplet: i686-pc-linux-gnu
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16898
next reply other threads:[~2004-08-06 14:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-06 14:32 pbrook at gcc dot gnu dot org [this message]
2004-08-07 22:09 ` [Bug fortran/16898] " pinskia at gcc dot gnu dot org
2004-12-10 13:02 ` paulthomas2 at wanadoo dot fr
2004-12-10 13:21 ` pbrook at gcc dot gnu dot org
2005-05-15 17:51 ` aj at gcc dot gnu dot org
2005-05-18 21:25 ` tobi at gcc dot gnu dot org
2005-06-04 21:00 ` cvs-commit at gcc dot gnu dot org
2005-06-04 21:00 ` tobi at gcc dot gnu dot org
2005-06-04 21:01 ` tobi 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=20040806143250.16898.pbrook@gcc.gnu.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).