From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6555 invoked by alias); 9 Jun 2011 18:29:53 -0000 Received: (qmail 6547 invoked by uid 22791); 9 Jun 2011 18:29:52 -0000 X-SWARE-Spam-Status: No, hits=-2.7 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00 X-Spam-Check-By: sourceware.org Received: from localhost (HELO gcc.gnu.org) (127.0.0.1) by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 09 Jun 2011 18:29:39 +0000 From: "edwintorok at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/49347] G++-4.6 Solaris incorrectly defines _RESTRICT_KYWD to __restrict X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: c++ X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: edwintorok at gmail dot com X-Bugzilla-Status: NEW X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Date: Thu, 09 Jun 2011 18:29:00 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2011-06/txt/msg00796.txt.bz2 http://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D49347 --- Comment #2 from T=C3=B6r=C3=B6k Edwin 201= 1-06-09 18:29:22 UTC --- (In reply to comment #1) > (In reply to comment #0) > >=20 > > Don't know where the #define to __restrict on __cplusplus comes from, b= ut it is > > wrong. >=20 > No, it's correct, see > http://gcc.gnu.org/onlinedocs/gcc/Restricted-Pointers.html >=20 >=20 > The bug is that G++ can't parse __restrict in an array parameter: >=20 > extern int f( char *const envp[__restrict] ); >=20 > The C front end accepts this, but not the C++ one. Is that planned to be fixed for the next release? If not then as a workaround that fix-includes header could #define _RESTRICY_KYWD to empty.