From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23752 invoked by alias); 19 Sep 2014 12:10:17 -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 23683 invoked by uid 48); 19 Sep 2014 12:10:09 -0000 From: "ubizjak at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/58192] G++ emits incorrect code when passing enum classes as function parameters Date: Fri, 19 Sep 2014 12:10: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.8.1 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: ubizjak at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P2 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: 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: 2014-09/txt/msg01925.txt.bz2 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D58192 --- Comment #8 from Uro=C5=A1 Bizjak --- (In reply to Jakub Jelinek from comment #7) > That is to be determined. Either it might be an x86_64 bug in passing su= ch > types, or FE issue, middle-end. Please note that the error also occurs with -m32, so it seems highly unlike= ly an x86_64 target-dependent bug. >>From gcc-bugs-return-462092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Fri Sep 19 12:24:34 2014 Return-Path: Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 3122 invoked by alias); 19 Sep 2014 12:24:34 -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 3084 invoked by uid 48); 19 Sep 2014 12:24:30 -0000 From: "jakub at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/63310] New: Ada bootstrap error with -fcompare-debug Date: Fri, 19 Sep 2014 12:24:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jakub at gcc dot gnu.org X-Bugzilla-Status: UNCONFIRMED 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 cc Message-ID: 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-09/txt/msg01926.txt.bz2 Content-length: 1474 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63310 Bug ID: 63310 Summary: Ada bootstrap error with -fcompare-debug Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: jakub at gcc dot gnu.org CC: charlet at gcc dot gnu.org, ebotcazou at gcc dot gnu.org My: ../configure --enable-languages=all,ada,obj-c++,lto,go --enable-checking=release; GCC_COMPARE_DEBUG=1 make -j48 bootstrap > LOG 2>&1 && GCC_COMPARE_DEBUG=1 make -j48 -k check > LOGC 2>&1; ../contrib/test_summary > LOGT 2>&1 bootstrap on x86_64 failed with: xgcc: error: a-rttiev.adb: -fcompare-debug failure It seems this is caused by gnat_write_global_declarations, which creates dummy_global decl AND corresponding varpool node for it (the former is not a problem I think, we only require that decls that are created for both -g and -g0 sort by DECL_UIDs the same (i.e. -g can have bigger gaps in the uids than -g0), but for cgraph nodes e.g. node->order is visible in the dumps), and for -g0 used_types_insert doesn't emit anything into types_used_by_cur_var_decl vector, while for -g if there are global vars it sometimes does. I have no idea what is dummy_global good for, but if you need it, it probably has to be created regardless of whether types_used_by_cur_var_decl vector is empty or not.