public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ondrej.certik at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/64244] [4.8/4.9/5 Regression] ICE at class.c:236 when using non_overridable Date: Tue, 16 Dec 2014 17:24:00 -0000 [thread overview] Message-ID: <bug-64244-4-8r0VD2a8tW@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64244-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64244 --- Comment #11 from Ondřej Čertík <ondrej.certik at gmail dot com> --- On Tue, Dec 16, 2014 at 9:47 AM, janus at gcc dot gnu.org <gcc-bugzilla@gcc.gnu.org> wrote: > https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64244 > > --- Comment #10 from janus at gcc dot gnu.org --- > (In reply to Ondřej Čertík from comment #9) >> Janus, thanks a lot for fixing this! > > You're welcome! > > >> Yes, it's part of a large code base. I'll try the trunk soon. > > That would be great. Since this bug is a regression, I plan to backport the fix > to the 4.8 and 4.9 branches. But before that it would be good to make sure that > no further problems appear. I think the NON_OVERRIDABLE attribute is not > incredibly well-tested at this point. I can compile 4.9.2 from source without problems, but when I follow the same procedure with the latest trunk (I used: https://github.com/gcc-mirror/gcc), I get: https://gist.github.com/certik/bbb96383e540efc8d6a3 And the part of config.log says: https://gist.github.com/certik/a308dbc6a26d12888ee6 i.e. the relevant error seems to be: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.15' not found So my system (RHEL6) libstdc++ library might be incompatible with the trunk, but I don't see why gcc couldn't compile. Any ideas how to fix this? >From gcc-bugs-return-470907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 16 17:26:16 2014 Return-Path: <gcc-bugs-return-470907-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 17001 invoked by alias); 16 Dec 2014 17:26: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 16955 invoked by uid 48); 16 Dec 2014 17:26:13 -0000 From: "marxin at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ipa/63851] [5 Regression] ipa-icf miscompiles gfortran.dg/assumed_rank_(8|9|10).f90 at -O2 and above Date: Tue, 16 Dec 2014 17:26:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ipa X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: wrong-code X-Bugzilla-Severity: normal X-Bugzilla-Who: marxin at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Priority: P1 X-Bugzilla-Assigned-To: marxin at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-63851-4-mDX0ZUMZBo@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-63851-4@http.gcc.gnu.org/bugzilla/> References: <bug-63851-4@http.gcc.gnu.org/bugzilla/> 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-12/txt/msg01914.txt.bz2 Content-length: 783 https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63851 --- Comment #5 from Martin Liška <marxin at gcc dot gnu.org> --- Yes, IPA ICF should respect 'restrict' attribute. May I ask you to rerun test suite with applied: diff --git a/gcc/ipa-icf-gimple.c b/gcc/ipa-icf-gimple.c index ec0290a..98f38ee 100644 --- a/gcc/ipa-icf-gimple.c +++ b/gcc/ipa-icf-gimple.c @@ -185,6 +185,9 @@ bool func_checker::compatible_types_p (tree t1, tree t2, if (TREE_CODE (t1) != TREE_CODE (t2)) return return_false_with_msg ("different tree types"); + if (TYPE_RESTRICT (t1) != TYPE_RESTRICT (t2)) + return return_false_with_msg ("restrict flags are different"); + if (!types_compatible_p (t1, t2)) return return_false_with_msg ("types are not compatible"); Thanks, Martin >From gcc-bugs-return-470908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Dec 16 17:30:00 2014 Return-Path: <gcc-bugs-return-470908-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 19119 invoked by alias); 16 Dec 2014 17:29:59 -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 19021 invoked by uid 48); 16 Dec 2014 17:29:56 -0000 From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug sanitizer/61591] Undefined behavior sanitizer does not catch builtin_unreachable's from impossible devirtualization Date: Tue, 16 Dec 2014 17:29:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: sanitizer X-Bugzilla-Version: 5.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: jamborm at gcc dot gnu.org X-Bugzilla-Status: ASSIGNED X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: jamborm at gcc dot gnu.org X-Bugzilla-Target-Milestone: 5.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-61591-4-2hpITFHHqT@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-61591-4@http.gcc.gnu.org/bugzilla/> References: <bug-61591-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-12/txt/msg01915.txt.bz2 Content-length: 246 https://gcc.gnu.org/bugzilla/show_bug.cgi?ida591 --- Comment #10 from Martin Jambor <jamborm at gcc dot gnu.org> --- Honza, given what you wrote in https://gcc.gnu.org/ml/gcc-patches/2014-12/msg01033.html do you want to take over this bug?
next prev parent reply other threads:[~2014-12-16 17:24 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-09 22:06 [Bug fortran/64244] New: internal compiler error " ondrej.certik at gmail dot com 2014-12-09 22:32 ` [Bug fortran/64244] [4.8/4.9/5 Regression] " dominiq at lps dot ens.fr 2014-12-15 13:28 ` [Bug fortran/64244] [4.8/4.9/5 Regression] ICE " janus at gcc dot gnu.org 2014-12-15 13:54 ` janus at gcc dot gnu.org 2014-12-15 15:30 ` janus at gcc dot gnu.org 2014-12-15 15:56 ` janus at gcc dot gnu.org 2014-12-15 20:14 ` janus at gcc dot gnu.org 2014-12-16 8:16 ` janus at gcc dot gnu.org 2014-12-16 8:23 ` janus at gcc dot gnu.org 2014-12-16 16:41 ` ondrej.certik at gmail dot com 2014-12-16 16:47 ` janus at gcc dot gnu.org 2014-12-16 17:24 ` ondrej.certik at gmail dot com [this message] 2014-12-16 20:46 ` janus at gcc dot gnu.org 2014-12-16 23:57 ` ondrej.certik at gmail dot com 2014-12-23 10:52 ` janus at gcc dot gnu.org 2014-12-23 19:07 ` janus at gcc dot gnu.org 2014-12-23 19:37 ` janus 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-64244-4-8r0VD2a8tW@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).