public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/12411] Missed -Wsequence-point on functions (example reduced from historical GCC source)
Date: Tue, 24 Aug 2021 06:15:55 +0000	[thread overview]
Message-ID: <bug-12411-4-kTLNCSdArQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-12411-4@http.gcc.gnu.org/bugzilla/>

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |WONTFIX
          Component|other                       |c
             Status|NEW                         |RESOLVED
           Severity|normal                      |enhancement

--- Comment #8 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
So thinking about this, I highly doubt we want to warn about this case as it is
hard to even know what we are warning about if two functions have side effects
that matter which order they are in.

Anyways I filed this bug report so I am closing as won't fix.

  parent reply	other threads:[~2021-08-24  6:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-12411-4@http.gcc.gnu.org/bugzilla/>
2020-05-12 22:12 ` [Bug other/12411] " rafael at espindo dot la
2021-08-24  6:15 ` pinskia at gcc dot gnu.org [this message]
2024-03-28  5:35 ` [Bug c/12411] " pinskia at gcc dot gnu.org
2024-03-29 16:34 ` egallager 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-12411-4-kTLNCSdArQ@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).