public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/49347] G++-4.6 Solaris incorrectly defines _RESTRICT_KYWD to __restrict
Date: Thu, 09 Jun 2011 18:24:00 -0000 [thread overview]
Message-ID: <bug-49347-4-o9tyPkLUv5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-49347-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49347
Jonathan Wakely <redi at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Last reconfirmed| |2011.06.09 18:24:01
Ever Confirmed|0 |1
--- Comment #1 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-06-09 18:24:01 UTC ---
(In reply to comment #0)
>
> Don't know where the #define to __restrict on __cplusplus comes from, but it is
> wrong.
No, it's correct, see
http://gcc.gnu.org/onlinedocs/gcc/Restricted-Pointers.html
The bug is that G++ can't parse __restrict in an array parameter:
extern int f( char *const envp[__restrict] );
The C front end accepts this, but not the C++ one.
next prev parent reply other threads:[~2011-06-09 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-09 18:05 [Bug c++/49347] New: " edwintorok at gmail dot com
2011-06-09 18:24 ` redi at gcc dot gnu.org [this message]
2011-06-09 18:29 ` [Bug c++/49347] " edwintorok at gmail dot com
2011-06-09 18:35 ` redi at gcc dot gnu.org
2011-06-10 18:32 ` [Bug c++/49347] G++ rejects Solaris spawn.h use of __restrict jason at gcc dot gnu.org
2011-07-25 15:21 ` ro at gcc dot gnu.org
2011-07-25 15:57 ` ro at gcc dot gnu.org
2011-07-25 15:59 ` ro at gcc dot gnu.org
2011-07-26 5:09 ` jason at gcc dot gnu.org
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-49347-4-o9tyPkLUv5@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).