public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Olivier Hainque <hainque@adacore.com>
To: libstdc++@gcc.gnu.org, gcc-patches@gcc.gnu.org
Cc: Olivier Hainque <hainque@adacore.com>,
	Rasmus Villemoes <rasmus.villemoes@prevas.dk>
Subject: [PATCH] Define _C99 in libstdc++ vxworks/os_defines.h
Date: Fri, 10 Dec 2021 16:06:38 +0100	[thread overview]
Message-ID: <FE28FC39-25F4-4C95-A323-CD698C372378@adacore.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 759 bytes --]

Hello,

The attached patch for libstdc++ / VxWorks helps building
the library for old versions of the OS, as witnessed with
VxWorks 6.9 in particular.

It explicitly requests C99 features from old system headers,
on which libstc++ relies since at least c++98. The specific
issue that exposed this was a failure to compile

  libstdc++-v3/src/c++17/floating_to_chars.cc

for VxWorks 6.9 with a batch of errors such as:

  error: 'FP_NAN' was not declared in this scope

The missing definitions are provided by the
system headers with guards on _HAS_C9X, which gets
internally defined when _C99 is.

Ok to commit?

Thanks in advance!

2021-12-07  Olivier Hainque  <hainque@adacore.com>

libstdc++-v3/

	* config/os/vxworks/os_defines.h: #define _C99.

Olivier


[-- Attachment #2: 0001-Define-_C99-in-libstdc-vxworks-os_defines.h.patch --]
[-- Type: application/octet-stream, Size: 1391 bytes --]

From f1051d0a9f2687fdf313b916d73b9b2d50e13ac2 Mon Sep 17 00:00:00 2001
From: Olivier Hainque <hainque@adacore.com>
Date: Fri, 19 Nov 2021 14:59:42 +0000
Subject: [PATCH] Define _C99 in libstdc++ vxworks/os_defines.h

To request C99 features from old system headers, on which
libstc++ relies since at least c++98. The specific issue that
exposed this was a failure to compile

  libstdc++-v3/src/c++17/floating_to_chars.cc

for VxWorks 6.9 with a batch of errors such as:

  error: 'FP_NAN' was not declared in this scope

The missing definitions are provided by the
system headers with guards on _HAS_C9X, which gets
internally defined when _C99 is.

2021-12-07  Olivier Hainque  <hainque@adacore.com>

libstdc++-v3/

	* config/os/vxworks/os_defines.h: #define _C99.
---
 libstdc++-v3/config/os/vxworks/os_defines.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/libstdc++-v3/config/os/vxworks/os_defines.h b/libstdc++-v3/config/os/vxworks/os_defines.h
index 75a68bc605b..78392dec30a 100644
--- a/libstdc++-v3/config/os/vxworks/os_defines.h
+++ b/libstdc++-v3/config/os/vxworks/os_defines.h
@@ -100,4 +100,9 @@
 #undef _NO_CPP_INLINES
 #define _NO_CPP_INLINES 1
 
+// libstdc++ relies on C99 features for virtually all versions of C++,
+// up to at least C++98.
+#undef _C99
+#define _C99 1
+
 #endif // _GLIBCXX_OS_DEFINES
-- 
2.25.1


             reply	other threads:[~2021-12-10 15:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-10 15:06 Olivier Hainque [this message]
2021-12-10 15:15 ` Rasmus Villemoes
2021-12-10 15:42   ` Jonathan Wakely
2021-12-10 16:15     ` Olivier Hainque

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=FE28FC39-25F4-4C95-A323-CD698C372378@adacore.com \
    --to=hainque@adacore.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=rasmus.villemoes@prevas.dk \
    /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).