public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "manu at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/63837] [5 Regression] r217391 causes kernel build errors with GCC_COMPARE_DEBUG=1
Date: Wed, 19 Nov 2014 15:34:00 -0000	[thread overview]
Message-ID: <bug-63837-4-HSO3MtEWOn@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63837-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63837

--- Comment #13 from Manuel López-Ibáñez <manu at gcc dot gnu.org> ---
(In reply to Jakub Jelinek from comment #12)
> Preapproved with proper ChangeLog entry.

Unfortunately, there seems to be a problem with the machine in the compile farm
that I use for gcc development, and I'm not able to finish a
bootstrap&regression test. I always get:

couldn't create output pipe for command: too many open files

even for a pristine copy of GCC. This didn't happen a few days ago. I didn't
have time yet to investigate what is wrong. If someone can bootstrap&regtest
the patch for me, I will commit it with proper changelog and send it to
gcc-patches.

(Of course, hints on how to fix the above problem are more than welcome. This
issue prevents me from doing any GCC development right now).
>From gcc-bugs-return-467522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org Wed Nov 19 15:36:20 2014
Return-Path: <gcc-bugs-return-467522-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-gcc-bugs@gcc.gnu.org
Received: (qmail 1194 invoked by alias); 19 Nov 2014 15:36:19 -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 1150 invoked by uid 48); 19 Nov 2014 15:36:15 -0000
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug lto/63963] [5 Regression] LTO doesn't work with __attribute__((__target__("sse4.2")))
Date: Wed, 19 Nov 2014 15:36:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: lto
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: hjl.tools at gmail dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P1
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 5.0
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_status cf_reconfirmed_on everconfirmed
Message-ID: <bug-63963-4-ZLv9Db9KPU@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-63963-4@http.gcc.gnu.org/bugzilla/>
References: <bug-63963-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-11/txt/msg01994.txt.bz2
Content-length: 484

https://gcc.gnu.org/bugzilla/show_bug.cgi?idc963

H.J. Lu <hjl.tools at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
   Last reconfirmed|                            |2014-11-19
     Ever confirmed|0                           |1

--- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> ---
It was caused by r217659.


  parent reply	other threads:[~2014-11-19 15:34 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-12 18:07 [Bug driver/63837] New: " trippels at gcc dot gnu.org
2014-11-12 23:56 ` [Bug driver/63837] " manu at gcc dot gnu.org
2014-11-13  2:41 ` trippels at gcc dot gnu.org
2014-11-13  2:47 ` pinskia at gcc dot gnu.org
2014-11-13  9:21 ` rguenth at gcc dot gnu.org
2014-11-13  9:57 ` trippels at gcc dot gnu.org
2014-11-13 13:36 ` manu at gcc dot gnu.org
2014-11-13 13:49 ` trippels at gcc dot gnu.org
2014-11-15  7:11 ` pinskia at gcc dot gnu.org
2014-11-15 11:16 ` manu at gcc dot gnu.org
2014-11-16 22:03 ` trippels at gcc dot gnu.org
2014-11-17 21:24 ` jakub at gcc dot gnu.org
2014-11-19 15:34 ` manu at gcc dot gnu.org [this message]
2014-11-19 15:40 ` trippels at gcc dot gnu.org
2014-11-19 16:38 ` jakub at gcc dot gnu.org
2014-11-19 18:12 ` jakub at gcc dot gnu.org
2014-11-19 18:38 ` trippels 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-63837-4-HSO3MtEWOn@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).