This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c++/49347] G++-4.6 Solaris incorrectly defines _RESTRICT_KYWD to __restrict
- From: "redi at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 9 Jun 2011 18:24:06 +0000
- Subject: [Bug c++/49347] G++-4.6 Solaris incorrectly defines _RESTRICT_KYWD to __restrict
- Auto-submitted: auto-generated
- References: <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.