[Bug c/68090] New: VLA compound literal -- "confused by earlier errors, bailing out"

[Bug c/68090] New: VLA compound literal -- "confused by earlier errors, bailing out"

[ch3root at openwall dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68090

            Bug ID: 68090
           Summary: VLA compound literal  -- "confused by earlier errors,
                    bailing out"
           Product: gcc
           Version: 5.2.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: ch3root at openwall dot com
  Target Milestone: ---

Compiling the following program:

int main() { (int [(0,1)]){0}; }

produce this:

compound-vla.c: In function ‘main’:
compound-vla.c:1:14: error: compound literal has variable size
 int main() { (int [(0,1)]){0}; }
              ^
compound-vla.c:1: confused by earlier errors, bailing out

The error message is fine but it should not "confuse" the compiler.
>From gcc-bugs-return-500517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Sun Oct 25 21:11:16 2015
Return-Path: <gcc-bugs-return-500517-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 23992 invoked by alias); 25 Oct 2015 21:11:16 -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
Delivered-To: mailing list gcc-bugs@gcc.gnu.org
Received: (qmail 23949 invoked by uid 48); 25 Oct 2015 21:11:12 -0000
From: "pault at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/61830] [4.9/5/6 regression] Memory leak with assignment to array of derived types with allocatable components
Date: Sun, 25 Oct 2015 21:11: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.8.3
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pault at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.4
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: cc
Message-ID: <bug-61830-4-NHD98CK3WI@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-61830-4@http.gcc.gnu.org/bugzilla/>
References: <bug-61830-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: 2015-10/txt/msg02072.txt.bz2
Content-length: 834

https://gcc.gnu.org/bugzilla/show_bug.cgi?ida830

Paul Thomas <pault at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pault at gcc dot gnu.org

--- Comment #6 from Paul Thomas <pault at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #5)
> The ICE is fixed by the patch submitted at
> https://gcc.gnu.org/ml/fortran/2015-10/msg00117.html.

The "memory leak" comes about because of the POINTER component map. This
allocation is still accessible at termination and is fixed by:

...snip....
! This gets rid of the "memory leak"
  if (associated (u%u(1)%map)) deallocate (u%u(1)%map)
  call free_v_field(u)
  call v%free()
  deallocate(av)
end program

[Bug c/68090] VLA compound literal -- "confused by earlier errors, bailing out"

[ebotcazou at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68090

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |ebotcazou at gcc dot gnu.org
         Resolution|---                         |WORKSFORME

--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> ---
The alternative is to emit further, possibly bogus error messages.

[Bug c/68090] VLA compound literal -- "confused by earlier errors, bailing out"

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68090

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Keywords|                            |error-recovery,
                   |                            |ice-on-valid-code
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|WORKSFORME                  |---

--- Comment #2 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Eric Botcazou from comment #1)
> The alternative is to emit further, possibly bogus error messages.

Not this still an internal compiler error followed by an error message so still
a bug.

[Bug c/68090] VLA compound literal -- "confused by earlier errors, bailing out"

[mpolacek at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=68090

Marek Polacek <mpolacek at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2015-10-26
                 CC|                            |mpolacek at gcc dot gnu.org
   Target Milestone|---                         |6.0
     Ever confirmed|0                           |1

--- Comment #3 from Marek Polacek <mpolacek at gcc dot gnu.org> ---
Confirmed.  I'll have a look, but likely not this week.