public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "law at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/58996] [4.9 regression] build failure in libcilkrts
Date: Thu, 16 Jan 2014 16:20:00 -0000	[thread overview]
Message-ID: <bug-58996-4-r7yOzWPwSZ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58996-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58996

--- Comment #17 from Jeffrey A. Law <law at redhat dot com> ---
If there's an interest, I could probably create a kickstart for a RHL8 VM
suitable for building GCC 4.9.   But it's a 10+ year old platform of marginal
value at best.

I'd be much more concerned about using cpu_set_t instead of the dynamically
sizing variants.  As Jakub noted cpu_set_t doesn't work with > 1024 processors
and it's been the source of some cross-distro problems as well.  If at all
possible we need to be moving away from using cpu_set_t to the newer APIs.

My recommendation would be to address the RHL8 problem (no cpu_set_t at all) as
efficiently as possible without burning huge amount of time on it.   Then a
separate BZ to track issues around moving away from cpu_set_t to the more
modern interfaces.


  parent reply	other threads:[~2014-01-16 16:20 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-58996-4@http.gcc.gnu.org/bugzilla/>
2013-11-05 11:17 ` rguenth at gcc dot gnu.org
2013-11-09 22:22 ` pinskia at gcc dot gnu.org
2013-11-19 13:33 ` rguenth at gcc dot gnu.org
2014-01-09 20:53 ` bviyer at gmail dot com
2014-01-09 21:08 ` jakub at gcc dot gnu.org
2014-01-09 21:28 ` bviyer at gmail dot com
2014-01-09 22:26 ` PHHargrove at lbl dot gov
2014-01-10 15:34 ` barry.m.tannenbaum at intel dot com
2014-01-10 16:11 ` jakub at gcc dot gnu.org
2014-01-10 18:12 ` PHHargrove at lbl dot gov
2014-01-15 19:46 ` bviyer at gmail dot com
2014-01-15 19:47 ` bviyer at gmail dot com
2014-01-16  6:56 ` PHHargrove at lbl dot gov
2014-01-16  7:11 ` jakub at gcc dot gnu.org
2014-01-16 14:08 ` barry.m.tannenbaum at intel dot com
2014-01-16 14:11 ` jakub at gcc dot gnu.org
2014-01-16 15:26 ` bviyer at gmail dot com
2014-01-16 16:20 ` law at redhat dot com [this message]
2014-01-20 17:50 ` bviyer at gcc dot gnu.org
2014-01-21 16:27 ` law at redhat 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-58996-4-r7yOzWPwSZ@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).