From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-444631-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 8248 invoked by alias); 22 Feb 2014 16:02:03 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
Received: (qmail 8191 invoked by uid 55); 22 Feb 2014 16:02:00 -0000
From: "paul.richard.thomas at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/59198] [4.7/4.8/4.9 Regression] ICE on cyclically dependent polymorphic types
Date: Sat, 22 Feb 2014 16:02:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: fortran
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: ice-on-valid-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: paul.richard.thomas at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P4
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.7.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-59198-4-k2Xqeeab98@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-59198-4@http.gcc.gnu.org/bugzilla/>
References: <bug-59198-4@http.gcc.gnu.org/bugzilla/>
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: 2014-02/txt/msg02388.txt.bz2

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59198

--- Comment #8 from paul.richard.thomas at gmail dot com <paul.richard.thomas at gmail dot com> ---
Hi Tobias,

I tried giving rng_t a component to avoid that - it didn't work :-(

Cheers

Paul

On 22 February 2014 16:35, burnus at gcc dot gnu.org
<gcc-bugzilla@gcc.gnu.org> wrote:
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59198
>
> --- Comment #7 from Tobias Burnus <burnus at gcc dot gnu.org> ---
> (In reply to Paul Thomas from comment #6)
>>         if (src->rng._data != 0B)
>>           {
>>             dst->rng._data = (struct rng_t *) __builtin_malloc ((unsigned
>> long) src->rng._vptr->_size);
>>             src->rng._vptr->_copy (src->rng._data, dst->rng._data);
>>           }
>
> Could this be caused by a NULL pointer? Namely,
>
> Malloc returns: "If size is 0, either a null pointer or a unique  pointer  that
>  can  be successfully passed to free() shall be returned."
>
> --
> You are receiving this mail because:
> You are on the CC list for the bug.