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 ipa/60325] [4.9 Regression] ICE in ipa_modify_formal_parameters, at ipa-prop.c compiling g++.dg/cilk-plus/CK/lambda_spawns.cc with LTO-profiledbootstrap build Date: Tue, 18 Mar 2014 11:19:00 -0000 [thread overview] Message-ID: <bug-60325-4-bUK0P3AKwU@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-60325-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60325 --- Comment #4 from Uroš Bizjak <ubizjak at gmail dot com> --- (In reply to Jakub Jelinek from comment #3) > Thus fixed? Hard to say, but the testsuite failure is gone and we have no testcase... >From gcc-bugs-return-446684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Tue Mar 18 11:20:12 2014 Return-Path: <gcc-bugs-return-446684-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org> Delivered-To: listarch-gcc-bugs@gcc.gnu.org Received: (qmail 1920 invoked by alias); 18 Mar 2014 11:20:12 -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 1860 invoked by uid 48); 18 Mar 2014 11:20:07 -0000 From: "mikpelinux at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/60504] [4.9 regression] many Ada testsuite regressions with gcc-4.9-20140309 on armv5tel-linux-gnueabi Date: Tue, 18 Mar 2014 11:20:00 -0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: ada X-Bugzilla-Version: 4.9.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: mikpelinux at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P4 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: 4.9.0 X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: <bug-60504-4-r3Ltl2JVU7@http.gcc.gnu.org/bugzilla/> In-Reply-To: <bug-60504-4@http.gcc.gnu.org/bugzilla/> References: <bug-60504-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-03/txt/msg01553.txt.bz2 Content-length: 395 http://gcc.gnu.org/bugzilla/show_bug.cgi?id`504 --- Comment #10 from Mikael Pettersson <mikpelinux at gmail dot com> --- (In reply to Eric Botcazou from comment #9) > That's good news, thanks. Did you do a testsuite run for all languages? Sorry, didn't have time for that -- the repeated 4.9 builds and tests caused other build-and-test jobs to pile up and I need to get those done first.
prev parent reply other threads:[~2014-03-18 11:19 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-02-23 22:13 [Bug ipa/60325] New: " ubizjak at gmail dot com 2014-02-24 8:31 ` [Bug ipa/60325] [4.9 Regression] " rguenth at gcc dot gnu.org 2014-03-09 21:54 ` ubizjak at gmail dot com 2014-03-18 11:13 ` jakub at gcc dot gnu.org 2014-03-18 11:19 ` ubizjak at gmail dot com [this message]
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-60325-4-bUK0P3AKwU@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).