public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rogi at linuxmail dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/47143] warning about const multidimensional array as function parameter
Date: Sat, 01 Jan 2011 13:16:00 -0000	[thread overview]
Message-ID: <bug-47143-4-JJoDyBnNS4@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47143-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Igor <rogi at linuxmail dot org> 2011-01-01 13:16:39 UTC ---
(In reply to comment #1)
> Not a bug.  The function parameters are of type "pointer to array[4] of const
> double" because const on an array type applies to the element type,
> recursively, and then the outermost array type, only, of a parameter of array
> type decays to a pointer, and the arguments passed are of type "pointer to
> array[4] of double" after array-to-pointer decay, and the only case where
> qualifiers are permitted to be added in assignment, argument passing etc. is
> qualifiers on the immediate pointer target, not those nested more deeply.

This was somewhat confusing to me. Did you mean that funcion expects:

pointer to array[4] of const doubles

and I am passing

pointer to const array[4] of doubles

instead?

This really seems pretty much teh same to me.

Correct me if I'm wrong please.


  parent reply	other threads:[~2011-01-01 13:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-01  5:38 [Bug c/47143] New: " rogi at linuxmail dot org
2011-01-01 11:25 ` [Bug c/47143] " rogi at linuxmail dot org
2011-01-01 12:02 ` jsm28 at gcc dot gnu.org
2011-01-01 13:02 ` rogi at linuxmail dot org
2011-01-01 13:16 ` rogi at linuxmail dot org [this message]
2011-01-01 15:06 ` jsm28 at gcc dot gnu.org
2011-01-01 15:42 ` rogi at linuxmail dot org
2011-01-01 16:36 ` jakub at gcc dot gnu.org
2021-08-01  6:41 ` muecker at gwdg dot de

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=bug-47143-4-JJoDyBnNS4@http.gcc.gnu.org/bugzilla/ \
    --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).