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 c/110205] Some new warnings from clang for the range code
Date: Mon, 12 Jun 2023 15:33:15 +0000	[thread overview]
Message-ID: <bug-110205-4-QLW66pWpv5@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-110205-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Andrew Macleod <amacleod@gcc.gnu.org>:

https://gcc.gnu.org/g:0ddc8c7871fdc7748315d9c09fcf29c2607a1077

commit r14-1735-g0ddc8c7871fdc7748315d9c09fcf29c2607a1077
Author: Andrew MacLeod <amacleod@redhat.com>
Date:   Mon Jun 12 09:47:43 2023 -0400

    Add some overrides.

            PR tree-optimization/110205
            * range-op-float.cc (range_operator::fold_range): Add default FII
            fold routine.
            * range-op-mixed.h (class operator_gt): Add missing final
overrides.
            * range-op.cc (range_op_handler::fold_range): Add RO_FII case.
            (operator_lshift ::update_bitmask): Add final override.
            (operator_rshift ::update_bitmask): Add final override.
            * range-op.h (range_operator::fold_range): Add FII prototype.

  parent reply	other threads:[~2023-06-12 15:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11  7:17 [Bug c/110205] New: " dcb314 at hotmail dot com
2023-06-12 13:30 ` [Bug c/110205] " amacleod at redhat dot com
2023-06-12 15:33 ` cvs-commit at gcc dot gnu.org [this message]
2023-07-10 14:19 ` dcb314 at hotmail dot com
2023-07-10 17:38 ` [Bug other/110205] " xry111 at gcc dot gnu.org
2023-07-28 20:37 ` cvs-commit at gcc dot gnu.org
2024-01-16 18:44 ` amacleod at redhat dot com
2024-01-20 17:24 ` pinskia 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-110205-4-QLW66pWpv5@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).