public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "dcb314 at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66068] New: error: type variant has different TYPE_VFIELD
Date: Fri, 08 May 2015 07:41:00 -0000	[thread overview]
Message-ID: <bug-66068-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 66068
           Summary: error: type variant has different TYPE_VFIELD
           Product: gcc
           Version: 6.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c
          Assignee: unassigned at gcc dot gnu.org
          Reporter: dcb314 at hotmail dot com
  Target Milestone: ---

Created attachment 35495
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=35495&action=edit
C source code

The attached code, when compiled by gcc trunk dated 20150506
and with flag -g, says this:

udns_resolver.c: In function ‘dns_new’:
udns_resolver.c:474:1: error: type variant has different TYPE_VFIELD

...

udns_resolver.c:474:1: internal compiler error: verify_type failed
0xe3782b verify_type(tree_node const*)
    ../../src/trunk/gcc/tree.c:12695
0x7de490 gen_type_die_with_usage
    ../../src/trunk/gcc/dwarf2out.c:20247
0x7cede2 gen_type_die_with_usage
    ../../src/trunk/gcc/dwarf2out.c:20334
0x7cd756 gen_type_die
    ../../src/trunk/gcc/dwarf2out.c:20431
>From gcc-bugs-return-485826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri May 08 07:45:49 2015
Return-Path: <gcc-bugs-return-485826-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 122982 invoked by alias); 8 May 2015 07:45:48 -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 122935 invoked by uid 48); 8 May 2015 07:45:43 -0000
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/66066] [6 Regression] r222889 causes bogus error: initializer element is not constant
Date: Fri, 08 May 2015 07:45: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: 6.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
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:
Message-ID: <bug-66066-4-Tph0O7ef0E@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-66066-4@http.gcc.gnu.org/bugzilla/>
References: <bug-66066-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-05/txt/msg00666.txt.bz2
Content-length: 454

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

--- Comment #2 from Markus Trippelsdorf <trippels at gcc dot gnu.org> ---
(In reply to Marek Polacek from comment #1)
> Yes, that is expected (in C99!).  See
> <https://gcc.gnu.org/ml/gcc-patches/2015-04/msg01946.html>.  New tests
> c90-left-shift-1.c and c99-left-shift-1.c explicitly test such behavior.

Hmm, that looks quite unfortunate from a qoi standpoint.
It will break tons of existing code.


             reply	other threads:[~2015-05-08  7:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-08  7:41 dcb314 at hotmail dot com [this message]
2015-05-11 14:56 ` [Bug debug/66068] [6 Regression] " mpolacek at gcc dot gnu.org
2015-05-11 14:56 ` mpolacek at gcc dot gnu.org
2015-05-11 15:02 ` mpolacek at gcc dot gnu.org
2015-06-16  5:22 ` trippels at gcc dot gnu.org
2015-08-13 20:21 ` matt at use dot net
2015-09-28 21:39 ` wilson at gcc dot gnu.org
2015-09-28 23:05 ` pinskia at gcc dot gnu.org
2015-10-28 20:02 ` wilson at gcc dot gnu.org
2015-10-28 20:06 ` wilson at gcc dot gnu.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-66068-4@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).