public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Joseph Myers <joseph@codesourcery.com>
To: Florian Weimer <fweimer@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>, <gcc@gcc.gnu.org>
Subject: Re: C89isms in the test suite
Date: Fri, 21 Oct 2022 20:57:15 +0000	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2210212055020.150427@digraph.polyomino.org.uk> (raw)
In-Reply-To: <87o7u5bknf.fsf@oldenburg.str.redhat.com>

On Fri, 21 Oct 2022, Florian Weimer via Gcc wrote:

> What's the expected default behavior for GCC 14 regarding old-style
> function definitions (function definitions which do not have a
> prototype)?  I assume if GCC 14 defaults to C2x mode, these no longer
> valid constructs would be rejected by default?  Based on some earlier

The existing situation is that it's a warning enabled by default in C2x 
mode.  You could of course argue for an error instead.

-- 
Joseph S. Myers
joseph@codesourcery.com

  parent reply	other threads:[~2022-10-21 20:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-21  8:40 Florian Weimer
2022-10-21  8:57 ` Jakub Jelinek
2022-10-21  9:17   ` Florian Weimer
2022-10-21  9:36     ` Jakub Jelinek
2022-10-21 10:01       ` Florian Weimer
2022-10-21 10:57         ` Florian Weimer
2022-10-21 21:00         ` Joseph Myers
2022-10-21 21:52           ` Florian Weimer
2022-10-21 20:57     ` Joseph Myers [this message]
2022-10-21 20:54 ` Joseph Myers
2022-10-21 21:46   ` Florian Weimer
2022-11-14  4:36 ` Sam James
2022-11-14  8:19   ` Florian Weimer
2022-11-15  5:05     ` Sam James
2022-11-21 11:12     ` Jakub Jelinek

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=alpine.DEB.2.22.394.2210212055020.150427@digraph.polyomino.org.uk \
    --to=joseph@codesourcery.com \
    --cc=fweimer@redhat.com \
    --cc=gcc@gcc.gnu.org \
    --cc=jakub@redhat.com \
    /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).