public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: gcc-patches@gcc.gnu.org
Cc: libstdc++@gcc.gnu.org, Jonathan Wakely <jwakely@redhat.com>
Subject: Unreviewed libstdc++ patch
Date: Tue, 24 Nov 2015 10:16:00 -0000	[thread overview]
Message-ID: <ydda8q3d7ni.fsf@lokon.CeBiTec.Uni-Bielefeld.DE> (raw)

The following libstdc++ patch

	[v3] Handle C++11 <math.h> overloads on Solaris 12
        https://gcc.gnu.org/ml/gcc-patches/2015-11/msg02075.html

has remained unreviewed for a week.  It fixes a Solaris 12 bootstrap
failure and is especially important for the gcc-5 branch at this point.
With the GCC 5.3 release imminent, it would be a pity to release without
this patch, S12 bootstrap broken and all the effort that went into
supporting S12 wasted.

Thanks.

	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

             reply	other threads:[~2015-11-24 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-24 10:16 Rainer Orth [this message]
2016-11-10 15:26 Rainer Orth
2023-03-01 12:37 Rainer Orth

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=ydda8q3d7ni.fsf@lokon.CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jwakely@redhat.com \
    --cc=libstdc++@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).