public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> 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 [thread overview] Message-ID: <bug-58192-4-qkEcWZeTsT@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-58192-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58192 --- Comment #8 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Jakub Jelinek from comment #7) > That is to be determined. Either it might be an x86_64 bug in passing such > types, or FE issue, middle-end. Please note that the error also occurs with -m32, so it seems highly unlikely 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: <gcc-bugs-return-462092-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> 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: <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 3084 invoked by uid 48); 19 Sep 2014 12:24:30 -0000 From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.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: <bug-63310-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-09/txt/msg01926.txt.bz2 Content-length: 1474 https://gcc.gnu.org/bugzilla/show_bug.cgi?idc310 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.
next prev parent reply other threads:[~2014-09-19 12:10 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-08-19 6:27 [Bug c++/58192] New: " temporal at gmail dot com 2013-08-19 6:29 ` [Bug c++/58192] " temporal at gmail dot com 2013-08-19 6:38 ` temporal at gmail dot com 2013-08-19 16:49 ` temporal at gmail dot com 2013-08-19 16:59 ` paolo.carlini at oracle dot com 2013-08-19 18:09 ` jakub at gcc dot gnu.org 2014-09-18 9:20 ` paolo.carlini at oracle dot com 2014-09-18 10:01 ` jakub at gcc dot gnu.org 2014-09-19 12:10 ` ubizjak at gmail dot com [this message] 2014-09-19 13:07 ` ubizjak at gmail dot com 2014-09-19 14:10 ` jakub at gcc dot gnu.org 2014-12-15 14:30 ` ubizjak at gmail dot com 2014-12-15 14:55 ` hjl.tools at gmail dot com 2014-12-15 16:01 ` hjl.tools at gmail dot com
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-58192-4-qkEcWZeTsT@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: linkBe 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).