public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "tgard at opentext dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/60984] [4.9 Regression] AIX: gcc-4.9.0 bootstrap fails in stage-2
Date: Mon, 05 May 2014 07:18:00 -0000 [thread overview]
Message-ID: <bug-60984-4-n5X9lMuCU2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60984-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=60984
--- Comment #13 from Torbjörn Gard <tgard at opentext dot com> ---
I got the same error this time.
I use bash but looking at config.log I see that /bin/sh is used. I have seen
nothing regarding this in the target-specific installation instructions.
I have restarted the build using CONFIG_SHELL=/usr/local/bin/bash. Maybe that
will make a difference :-)
>From gcc-bugs-return-450532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Mon May 05 07:37:10 2014
Return-Path: <gcc-bugs-return-450532-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 11941 invoked by alias); 5 May 2014 07:37:09 -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 11905 invoked by uid 55); 5 May 2014 07:37:07 -0000
From: "amker at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/60363] [4.9/4.10 Regression]: logical_op_short_circuit, gcc.dg/tree-ssa/ssa-dom-thread-4.c scan-tree-dump-times dom1 "Threaded" 4
Date: Mon, 05 May 2014 07:37:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: tree-optimization
X-Bugzilla-Version: 4.9.0
X-Bugzilla-Keywords: xfail
X-Bugzilla-Severity: normal
X-Bugzilla-Who: amker at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.9.1
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-60363-4-FfiC2Ku5O4@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-60363-4@http.gcc.gnu.org/bugzilla/>
References: <bug-60363-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-05/txt/msg00224.txt.bz2
Content-length: 851
http://gcc.gnu.org/bugzilla/show_bug.cgi?id`363
--- Comment #14 from amker at gcc dot gnu.org ---
Author: amker
Date: Mon May 5 07:36:30 2014
New Revision: 210059
URL: http://gcc.gnu.org/viewcvs?rev!0059&root=gcc&view=rev
Log:
PR tree-optimization/60363
* gcc/tree-ssa-threadupdate.c (get_value_locus_in_path): New.
(copy_phi_args): New parameters. Call get_value_locus_in_path.
(update_destination_phis): New parameter.
(create_edge_and_update_destination_phis): Ditto.
(ssa_fix_duplicate_block_edges): Pass new arguments.
(thread_single_edge): Ditto.
PR tree-optimization/60363
* gcc.dg/tree-ssa/ssa-dom-thread-4.c: Revert XFAIL test.
Modified:
trunk/gcc/ChangeLog
trunk/gcc/testsuite/ChangeLog
trunk/gcc/testsuite/gcc.dg/tree-ssa/ssa-dom-thread-4.c
trunk/gcc/tree-ssa-threadupdate.c
next prev parent reply other threads:[~2014-05-05 7:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 9:05 [Bug bootstrap/60984] New: " tgard at opentext dot com
2014-04-28 13:46 ` [Bug bootstrap/60984] " dje at gcc dot gnu.org
2014-04-28 19:23 ` dje at gcc dot gnu.org
2014-04-28 19:41 ` dje at gcc dot gnu.org
2014-04-28 22:09 ` dje at gcc dot gnu.org
2014-04-29 7:49 ` jakub at gcc dot gnu.org
2014-04-29 7:55 ` [Bug bootstrap/60984] [4.9 Regression] " rguenth at gcc dot gnu.org
2014-04-29 12:54 ` dje at gcc dot gnu.org
2014-04-29 14:11 ` tgard at opentext dot com
2014-04-29 17:01 ` dje at gcc dot gnu.org
2014-04-29 17:56 ` dje at gcc dot gnu.org
2014-05-02 7:59 ` tgard at opentext dot com
2014-05-02 13:29 ` tgard at opentext dot com
2014-05-04 20:13 ` dje at gcc dot gnu.org
2014-05-05 7:18 ` tgard at opentext dot com [this message]
2014-05-05 15:25 ` tgard at opentext dot com
2014-05-08 1:18 ` dje at gcc dot gnu.org
2014-05-08 2:05 ` dje at gcc dot gnu.org
2014-05-08 3:00 ` dje at gcc dot gnu.org
2014-05-08 17:42 ` dje at gcc dot gnu.org
2014-05-09 14:29 ` hubicka at gcc dot gnu.org
2014-05-09 15:44 ` dje at gcc dot gnu.org
2014-05-09 15:53 ` dje at gcc dot gnu.org
2014-05-10 14:57 ` dje at gcc dot gnu.org
2014-05-10 15:34 ` dje at gcc dot gnu.org
2014-05-20 22:48 ` hubicka at ucw dot cz
2014-05-20 23:02 ` dje at gcc dot gnu.org
2014-05-20 23:23 ` hubicka at ucw dot cz
2014-05-21 1:45 ` dje at gcc dot gnu.org
2014-05-21 5:40 ` hubicka at gcc dot gnu.org
2014-05-21 5:42 ` hubicka at gcc dot gnu.org
2014-05-21 5:45 ` hubicka at gcc dot gnu.org
2014-05-22 12:11 ` tgard at opentext dot com
2014-05-22 21:06 ` fbissey at slingshot dot co.nz
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-60984-4-n5X9lMuCU2@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).