From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-prs-return-29988-listarch-gcc-prs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 3211 invoked by alias); 24 Feb 2003 06:36:00 -0000
Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Archive: <http://gcc.gnu.org/ml/gcc-prs/>
List-Post: <mailto:gcc-prs@gcc.gnu.org>
List-Help: <mailto:gcc-prs-help@gcc.gnu.org>
Sender: gcc-prs-owner@gcc.gnu.org
Received: (qmail 3191 invoked by uid 71); 24 Feb 2003 06:36:00 -0000
Resent-Date: 24 Feb 2003 06:36:00 -0000
Resent-Message-ID: <20030224063600.3190.qmail@sources.redhat.com>
Resent-From: gcc-gnats@gcc.gnu.org (GNATS Filer)
Resent-Cc: gcc-prs@gcc.gnu.org, gcc-bugs@gcc.gnu.org
Resent-Reply-To: gcc-gnats@gcc.gnu.org, bradley-gnu@bradley.lcs.mit.edu
Received: (qmail 995 invoked by uid 48); 24 Feb 2003 06:27:23 -0000
Message-Id: <20030224062723.994.qmail@sources.redhat.com>
Date: Mon, 24 Feb 2003 06:36:00 -0000
From: bradley-gnu@bradley.lcs.mit.edu
Reply-To: bradley-gnu@bradley.lcs.mit.edu
To: gcc-gnats@gcc.gnu.org
X-Send-Pr-Version: gnatsweb-2.9.3 (1.1.1.1.2.31)
Subject: driver/9822: The "%c" spec option produces: gcc: spec failure: unrecognized spec option 'c'
X-SW-Source: 2003-02/txt/msg01225.txt.bz2
List-Id: <gcc-prs.sourceware.org>


>Number:         9822
>Category:       driver
>Synopsis:       The "%c" spec option produces: gcc: spec failure: unrecognized spec option 'c'
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          doc-bug
>Submitter-Id:   net
>Arrival-Date:   Mon Feb 24 06:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     bradley-gnu@bradley.lcs.mit.edu
>Release:        gcc-3.2.1
>Organization:
>Environment:

>Description:
I tried to write a spec file that used the %c option, but it is no longer accepted by the driver.  The error is printed by line 5234 of gcc.c.

The gcc.info documentation says that %c is accepted, however:
> `%c'
>     Process the `signed_char' spec.  This is intended to be used to
>     tell cpp whether a char is signed.  It typically has the
>     definition:
>          %{funsigned-char:-D__CHAR_UNSIGNED__}

This is probably a documentation bug, rather than a code bug.

The documentation on the spec files seems quite out-of-date.
For example, I cannot figure out, from the documentation, what does this entry mean in the spec file.
 %{fsigned-char&unsigned-char}


>How-To-Repeat:

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted: