From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 93559 invoked by alias); 28 Sep 2015 06:59:55 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 93531 invoked by uid 48); 28 Sep 2015 06:59:51 -0000 From: "baradi09 at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/67740] New: Wrong association status of allocatable character pointer in derived types Date: Mon, 28 Sep 2015 06:59:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: fortran X-Bugzilla-Version: 5.2.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: baradi09 at gmail dot com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status bug_severity priority component assigned_to reporter target_milestone attachments.created Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg02143.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D67740 Bug ID: 67740 Summary: Wrong association status of allocatable character pointer in derived types Product: gcc Version: 5.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: fortran Assignee: unassigned at gcc dot gnu.org Reporter: baradi09 at gmail dot com Target Milestone: --- Created attachment 36405 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=3D36405&action=3Dedit Self containing example demonstrating the issue. Dear all, I've found the following problem with gfortran 5.2.0: Let's take a derived = type (Base) with a pointer component (string) of the type deferred length charac= ter, one instance of this derived type and two pointers (p1 and p2) pointing to = this one instance. While 'associated(p1, p2)' correctly detects the equivalence = of the two pointers, 'associated(p1%string, p2%string)' wrongly indicates an inequivalence of the pointer components. Best, B=C3=A1lint >>From gcc-bugs-return-498166-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon Sep 28 07:11:16 2015 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 115229 invoked by alias); 28 Sep 2015 07:11:16 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Delivered-To: mailing list gcc-bugs@gcc.gnu.org Received: (qmail 115202 invoked by uid 48); 28 Sep 2015 07:11:12 -0000 From: "trippels at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/67739] name clash between builtin functions and local variables when optimization is on Date: Mon, 28 Sep 2015 07:11:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Version: 4.9.3 X-Bugzilla-Keywords: X-Bugzilla-Severity: major X-Bugzilla-Who: trippels at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-SW-Source: 2015-09/txt/msg02144.txt.bz2 Content-length: 516 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67739 Markus Trippelsdorf changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |trippels at gcc dot gnu.org --- Comment #1 from Markus Trippelsdorf --- Well just don't name the array sincosf. Or use -fno-builtin-sin. I can only reproduce the issue with 4.9.3 and -Ofast.