public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/20230] GCC generates non-compliant warnings for qualifier promotion
Date: Sun, 27 Feb 2005 18:57:00 -0000	[thread overview]
Message-ID: <20050227132059.20098.qmail@sourceware.org> (raw)
In-Reply-To: <20050227052446.20230.kmk@ssl.org>


------- Additional Comments From falk at debian dot org  2005-02-27 13:20 -------
(In reply to comment #5)

> Am I wrong? Where does it state in the C standard that you cannot perform a
> multi-level qualifier promotion?

Nowhere. It follows from the fact that it is not allowed explicitly in 
6.5.16.1. The demand is:

  -- both operands are pointers to qualified or unqualified versions
  of compatible types, and the type pointed to by the left has all the
  qualifiers of the type pointed to by the right;

but "pointer to char" is not compatible with "const pointer to const char".


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=20230


  parent reply	other threads:[~2005-02-27 13:21 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-27 16:17 [Bug debug/20230] New: " kmk at ssl dot org
2005-02-27 16:19 ` [Bug debug/20230] " pinskia at gcc dot gnu dot org
2005-02-27 16:32 ` [Bug c/20230] " pinskia at gcc dot gnu dot org
2005-02-27 16:33 ` pinskia at gcc dot gnu dot org
2005-02-27 17:14 ` kmk at ssl dot org
2005-02-27 18:16 ` falk at debian dot org
2005-02-27 18:32 ` kmk at ssl dot org
2005-02-27 18:47 ` joseph at codesourcery dot com
2005-02-27 18:57 ` falk at debian dot org [this message]
2005-02-28  6:35 ` kmk at ssl dot org
2005-02-28  8:27 ` kmk at ssl dot org
2005-02-28 10:00 ` joseph at codesourcery dot com
2005-02-28 10:27 ` kmk at ssl dot org
     [not found] <bug-20230-10174@http.gcc.gnu.org/bugzilla/>
2005-12-07 17:10 ` pinskia at gcc dot gnu dot org
2005-12-07 17:10 ` pinskia at gcc dot gnu dot 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=20050227132059.20098.qmail@sourceware.org \
    --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).