From: Sebastian Huber <sebastian.huber@embedded-brains.de>
To: newlib@sourceware.org
Subject: Re: newlib header breaks restricted pointers in C++
Date: Fri, 28 Jul 2023 16:15:41 +0200 [thread overview]
Message-ID: <b104f1c6-9012-5e7d-50cb-7003f1dec472@embedded-brains.de> (raw)
In-Reply-To: <ZMIyGF/s09GhE228@calimero.vinschen.de>
On 27.07.23 11:00, Corinna Vinschen wrote:
> Let's compare with the GLibc version:
>
> /* __restrict is known in EGCS 1.2 and above, and in clang.
> It works also in C++ mode (outside of arrays), but only when spelled
> as '__restrict', not 'restrict'. */
> #if !(__GNUC_PREREQ (2,92) || __clang_major__ >= 3)
> # if defined __STDC_VERSION__ && __STDC_VERSION__ >= 199901L
> # define __restrict restrict
> # else
> # define __restrict /* Ignore */
> # endif
> #endif
>
> So the expression is the same, just the version check makes more sense.
>
> Shall we match our version expression to the GLibc expression?
Yes, this makes sense. However, do we care about GCC < 2.92 and clang < 3?
--
embedded brains GmbH
Herr Sebastian HUBER
Dornierstr. 4
82178 Puchheim
Germany
email: sebastian.huber@embedded-brains.de
phone: +49-89-18 94 741 - 16
fax: +49-89-18 94 741 - 08
Registergericht: Amtsgericht München
Registernummer: HRB 157899
Vertretungsberechtigte Geschäftsführer: Peter Rasmussen, Thomas Dörfler
Unsere Datenschutzerklärung finden Sie hier:
https://embedded-brains.de/datenschutzerklaerung/
next prev parent reply other threads:[~2023-07-28 14:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 22:23 Bruno De Fraine
2023-07-25 17:35 ` Corinna Vinschen
2023-07-25 17:46 ` Sebastian Huber
2023-07-25 18:48 ` Corinna Vinschen
2023-07-25 23:48 ` Steven J Abner
2023-07-27 9:00 ` Corinna Vinschen
2023-07-28 14:15 ` Sebastian Huber [this message]
2023-07-28 14:42 ` Joel Sherrill
2023-07-31 11:04 ` Bruno De Fraine
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=b104f1c6-9012-5e7d-50cb-7003f1dec472@embedded-brains.de \
--to=sebastian.huber@embedded-brains.de \
--cc=newlib@sourceware.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).