public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "lukaszcz18 at wp dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/107954] Support -std=c23/gnu23 as aliases of -std=c2x/gnu2x
Date: Sat, 03 Dec 2022 08:38:24 +0000	[thread overview]
Message-ID: <bug-107954-4-qu4gx4VfHm@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107954-4@http.gcc.gnu.org/bugzilla/>

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

Jamaika <lukaszcz18 at wp dot pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |lukaszcz18 at wp dot pl

--- Comment #2 from Jamaika <lukaszcz18 at wp dot pl> ---
I shouldn't be writing as an outsider.
I don't know what c2x accepts.
For gcc 11.3.1 and c++20 I am forced to use c2x.
For example, compiling HTJ2K grok c++20 and zlib shows that zlib does not
conform to c++20 standards and some functions are deprecated.

adler32.c: In function 'adler32_z':
adler32.c:63:15: warning: old-style function definition
[-Wold-style-definition]
   63 | uLong ZEXPORT adler32_z(adler, buf, len)
      |               ^~~~~~~~~
adler32.c: In function 'adler32':
adler32.c:134:15: warning: old-style function definition
[-Wold-style-definition]
  134 | uLong ZEXPORT adler32(adler, buf, len)
      |               ^~~~~~~
adler32.c: In function 'adler32_combine_':
adler32.c:143:13: warning: old-style function definition
[-Wold-style-definition]
  143 | local uLong adler32_combine_(adler1, adler2, len2)
      |             ^~~~~~~~~~~~~~~~
adler32.c: In function 'adler32_combine':
adler32.c:172:15: warning: old-style function definition
[-Wold-style-definition]
  172 | uLong ZEXPORT adler32_combine(adler1, adler2, len2)
      |               ^~~~~~~~~~~~~~~
adler32.c: In function 'adler32_combine64':
adler32.c:180:15: warning: old-style function definition
[-Wold-style-definition]
  180 | uLong ZEXPORT adler32_combine64(adler1, adler2, len2)
      |               ^~~~~~~~~~~~~~~~~
compress.c: In function 'compress2':
compress.c:22:13: warning: old-style function definition
[-Wold-style-definition]
   22 | int ZEXPORT compress2(dest, destLen, source, sourceLen, level)
      |             ^~~~~~~~~
compress.c: In function 'compress':
compress.c:68:13: warning: old-style function definition
[-Wold-style-definition]
   68 | int ZEXPORT compress(dest, destLen, source, sourceLen)
      |             ^~~~~~~~
compress.c: In function 'compressBound':
compress.c:81:15: warning: old-style function definition
[-Wold-style-definition]
   81 | uLong ZEXPORT compressBound(sourceLen)
      |               ^~~~~~~~~~~~~
crc32.c: In function 'byte_swap':
crc32.c:126:16: warning: old-style function definition [-Wold-style-definition]
  126 | local z_word_t byte_swap(word)
      |                ^~~~~~~~~
crc32.c: In function 'multmodp':
crc32.c:551:15: warning: old-style function definition [-Wold-style-definition]
  551 | local z_crc_t multmodp(a, b)
      |               ^~~~~~~~
crc32.c: In function 'x2nmodp':
crc32.c:575:15: warning: old-style function definition [-Wold-style-definition]
  575 | local z_crc_t x2nmodp(n, k)
      |               ^~~~~~~
crc32.c: In function 'crc_word':
crc32.c:726:15: warning: old-style function definition [-Wold-style-definition]
  726 | local z_crc_t crc_word(data)
      |               ^~~~~~~~
crc32.c: In function 'crc_word_big':
crc32.c:735:16: warning: old-style function definition [-Wold-style-definition]
  735 | local z_word_t crc_word_big(data)
      |                ^~~~~~~~~~~~
crc32.c: In function 'crc32_z':
crc32.c:748:23: warning: old-style function definition [-Wold-style-definition]
  748 | unsigned long ZEXPORT crc32_z(crc, buf, len)
      |                       ^~~~~~~
crc32.c: In function 'crc32':
crc32.c:1072:23: warning: old-style function definition
[-Wold-style-definition]
 1072 | unsigned long ZEXPORT crc32(crc, buf, len)
      |                       ^~~~~

  parent reply	other threads:[~2022-12-03  8:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-02 19:25 [Bug driver/107954] New: " romain.geissler at amadeus dot com
2022-12-02 21:00 ` [Bug c/107954] " pinskia at gcc dot gnu.org
2022-12-03  8:38 ` lukaszcz18 at wp dot pl [this message]
2022-12-07  0:41 ` joseph at codesourcery dot com
2023-08-10 23:07 ` romain.geissler at amadeus dot com
2023-08-11 15:48 ` joseph at codesourcery dot com
2023-10-19 13:49 ` daniel.lundin.mail at gmail dot com
2023-11-06 15:03 ` cvs-commit at gcc dot gnu.org
2023-11-08  0:25 ` jsm28 at gcc dot gnu.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=bug-107954-4-qu4gx4VfHm@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).