public inbox for gcc-cvs@sourceware.org
help / color / mirror / Atom feed
From: Thomas Schwinge <tschwinge@gcc.gnu.org>
To: gcc-cvs@gcc.gnu.org
Subject: [gcc r12-7909] options: Remove 'gcc/c-family/c.opt:Warray-bounds' option definition record
Date: Wed, 30 Mar 2022 06:58:32 +0000 (GMT)	[thread overview]
Message-ID: <20220330065832.54CA73858403@sourceware.org> (raw)

https://gcc.gnu.org/g:78291af555e957a149c00a68f0fefdc419feee6f

commit r12-7909-g78291af555e957a149c00a68f0fefdc419feee6f
Author: Thomas Schwinge <thomas@codesourcery.com>
Date:   Thu Mar 24 22:17:23 2022 +0100

    options: Remove 'gcc/c-family/c.opt:Warray-bounds' option definition record
    
    A one-argument form of the 'LangEnabledBy' option property isn't defined,
    and effectively appears to be a no-op.  Removing that one, the
    'gcc/c-family/c.opt:Warray-bounds' option definition record becomes empty,
    and doesn't add anything over 'gcc/common.opt:Warray-bounds', and may thus
    be removed entirely.  This only changes 'build-gcc/gcc/optionlist'
    accordingly, but no other generated files.
    
    Clean-up after r262912/commit 0d7f90652080c42cddca6f9b68f6895218c70880
    "PR middle-end/82063 - issues with arguments enabled by -Wall".
    
            gcc/c-family/
            * c.opt (Warray-bounds): Remove.

Diff:
---
 gcc/c-family/c.opt | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/gcc/c-family/c.opt b/gcc/c-family/c.opt
index 790d47caf0a..3c2ec7744b0 100644
--- a/gcc/c-family/c.opt
+++ b/gcc/c-family/c.opt
@@ -342,10 +342,6 @@ Wno-alloca-larger-than
 C ObjC C++ LTO ObjC++ Alias(Walloca-larger-than=,18446744073709551615EiB,none) Warning
 Disable Walloca-larger-than= warning.  Equivalent to Walloca-larger-than=<SIZE_MAX> or larger.
 
-Warray-bounds
-LangEnabledBy(C ObjC C++ LTO ObjC++)
-; in common.opt
-
 Warray-bounds=
 LangEnabledBy(C ObjC C++ LTO ObjC++,Wall,1,0)
 ; in common.opt


                 reply	other threads:[~2022-03-30  6:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20220330065832.54CA73858403@sourceware.org \
    --to=tschwinge@gcc.gnu.org \
    --cc=gcc-cvs@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).