public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bernd Edlinger <bernd.edlinger@hotmail.de>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>,
	"libstdc++@gcc.gnu.org" <libstdc++@gcc.gnu.org>
Cc: Jonathan Wakely <jwakely@redhat.com>
Subject: [PING] [PATCH, libstdc++] Add missing free-standing headers to install rule
Date: Wed, 16 Mar 2016 08:32:00 -0000	[thread overview]
Message-ID: <AM4PR07MB1571A35FB57B155CD9C79B83E48A0@AM4PR07MB1571.eurprd07.prod.outlook.com> (raw)
In-Reply-To: <VI1PR07MB0911F2B49AE4FBDDD72EEA2EE4B20@VI1PR07MB0911.eurprd07.prod.outlook.com>

Ping...

Hi,

when the free-standing libstdc++-headers are installed, the C++ header
file <new> does not always compile, because it includes <exception> and this
includes under certain conditions (__cplusplus >= 201103L &&
ATOMIC_INT_LOCK_FREE > 1) the header file <bits/nested_exception.h>
but that fails to compile because it needs <bits/move.h> which is not installed.
This condition depends on the target, and for instance an arm-eabi
eCos compiler fails to compile <new> with -mcpu=cortex-a9 and the
default C++ standard option, while it is OK with ARMv4 CPUs.

Therefore this patch adds move.h and concept_check.h to the installed headers,
unconditionally.

I've verified that the <new> header compiles on an eCos cross compiler.

Boot-strapped and regression-tested on x86_64-pc-linux-gnu.
Is it OK for trunk?


Thanks
Bernd.

  reply	other threads:[~2016-03-16  8:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-09  3:34 Bernd Edlinger
2016-03-16  8:32 ` Bernd Edlinger [this message]
2016-03-22  7:30   ` [PING**2] " Bernd Edlinger
2016-03-22 15:55     ` Jonathan Wakely
2016-03-22 19:00       ` Bernd Edlinger
2016-03-22 20:34         ` Jonathan Wakely
2016-03-22 21:28           ` Bernd Edlinger
2016-03-22 23:12             ` Jonathan Wakely

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=AM4PR07MB1571A35FB57B155CD9C79B83E48A0@AM4PR07MB1571.eurprd07.prod.outlook.com \
    --to=bernd.edlinger@hotmail.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).