public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/108560] builtin_va_arg_pack_len is documented to return size_t, but actually returns int
Date: Wed, 03 May 2023 15:20:53 +0000	[thread overview]
Message-ID: <bug-108560-4-a51nWevx5m@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108560-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108560

--- Comment #7 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The releases/gcc-10 branch has been updated by Jakub Jelinek
<jakub@gcc.gnu.org>:

https://gcc.gnu.org/g:5ebdbf03c7fb77c2535faca020e25a16658e8cb6

commit r10-11358-g5ebdbf03c7fb77c2535faca020e25a16658e8cb6
Author: Jakub Jelinek <jakub@redhat.com>
Date:   Fri Jan 27 11:17:35 2023 +0100

    doc: Fix up return type of __builtin_va_arg_pack_len [PR108560]

    __builtin_va_arg_pack_len as implemented returned int since its
introduction
    in 2007.  The initial documentation didn't mention any return type,
    which changed in 2010 in r0-103077-gab940b73bfabe2cec4 during some
    documentation formatting cleanups
    https://gcc.gnu.org/legacy-ml/gcc-patches/2010-09/msg01632.html
    I can understand that for formatting some type was needed there
    but what exactly hasn't been really discussed.

    So, I think we should change documentation to match the implementation,
    rather than change implementation to match the documentation.
    Most people don't use more than 2147483647 arguments to inline functions,
    and on poor targets with 16-bit ints I bet even having more than 65535
    arguments to inline functions would be highly unexpected.

    2023-01-27  Jakub Jelinek  <jakub@redhat.com>

            PR other/108560
            * doc/extend.texi: Fix up return type of __builtin_va_arg_pack_len
            from size_t to int.

    (cherry picked from commit 16f30680f403891556da2ad6329fcef9dc9b47db)

      parent reply	other threads:[~2023-05-03 15:20 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-26 15:50 [Bug c++/108560] New: " jens.seifert at de dot ibm.com
2023-01-26 16:14 ` [Bug c++/108560] " jakub at gcc dot gnu.org
2023-01-26 16:17 ` [Bug other/108560] " jakub at gcc dot gnu.org
2023-01-27 10:18 ` cvs-commit at gcc dot gnu.org
2023-01-27 10:19 ` jakub at gcc dot gnu.org
2023-02-10 17:46 ` cvs-commit at gcc dot gnu.org
2023-05-02 20:13 ` cvs-commit at gcc dot gnu.org
2023-05-03 15:20 ` cvs-commit at gcc dot gnu.org [this message]

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-108560-4-a51nWevx5m@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).