From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29690 invoked by alias); 2 Jul 2006 16:11:58 -0000 Received: (qmail 29656 invoked by uid 48); 2 Jul 2006 16:11:47 -0000 Date: Sun, 02 Jul 2006 16:11:00 -0000 Message-ID: <20060702161147.29655.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug c/28152] Diagnostic about wrong use _Complex prints __complex__ In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "pinskia at gcc dot gnu dot org" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2006-07/txt/msg00043.txt.bz2 List-Id: ------- Comment #4 from pinskia at gcc dot gnu dot org 2006-07-02 16:11 ------- (In reply to comment #3) > Indeed. However, we can approximate a fix by testing whether we're > compiling under C99, GNU99, or just C90, or C++. That would not work as _Complex is accepted in GNU90 more and with the C++ front-end by default. In fact "_Complex float t;" is accepted with the C++ front-end even with -pedantic which seems wrong and that would be a different but. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28152