public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Momchil Velikov <velco@fadata.bg>
To: gcc@gcc.gnu.org
Subject: PROMOTE_PROTOTYPES nonstandard ?
Date: Wed, 24 Jul 2002 11:38:00 -0000	[thread overview]
Message-ID: <87n0shs7sa.fsf@fadata.bg> (raw)


ISO/IEC 9899:1999 - 6.5.2.2  Function calls

       [#7] If the expression that denotes the called function  has
       a  type  that  does  include  a prototype, the arguments are
       implicitly converted, as if by assignment, to the  types  of
       the  corresponding  parameters,  taking  the  type  of  each
       parameter to be the  unqualified  version  of  its  declared
       type.    The  ellipsis  notation  in  a  function  prototype
       declarator causes argument type conversion to stop after the
       last  declared  parameter.   The default argument promotions
       are performed on trailing arguments.

       [#8] No  other  conversions  are  performed  implicitly;

gccint.texi
`PROMOTE_PROTOTYPES'
     A C expression whose value is nonzero if an argument declared in a
     prototype as an integral type smaller than `int' should actually
     be passed as an `int'.  

Does that mean that targets, which #define PROMOTE_PROTOTYPES 1
(almost all) are non iso9899:1999 compliant ?

~velco

             reply	other threads:[~2002-07-24 11:53 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-24 11:38 Momchil Velikov [this message]
2002-07-24 12:16 ` Andreas Schwab

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=87n0shs7sa.fsf@fadata.bg \
    --to=velco@fadata.bg \
    --cc=gcc@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).