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 tree-optimization/108828] ivopts silencing gcc.dg/Wuse-after-free-2.c:115
Date: Tue, 28 Feb 2023 01:05:05 +0000	[thread overview]
Message-ID: <bug-108828-4-JoCKMj0QFQ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-108828-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Hans-Peter Nilsson <hp@gcc.gnu.org>:

https://gcc.gnu.org/g:8c58f4b798177d419c5af37b7e23c490849f2d45

commit r13-6364-g8c58f4b798177d419c5af37b7e23c490849f2d45
Author: Hans-Peter Nilsson <hp@axis.com>
Date:   Fri Feb 24 17:22:02 2023 +0100

    testsuite: Add -fno-ivopts to gcc.dg/Wuse-after-free-2.c, PR108828

    For cris-elf before this patch, ever since it was added,
    this test gets:

    Running /x/gcc/testsuite/gcc.dg/dg.exp ...
    FAIL: gcc.dg/Wuse-after-free-2.c  (test for warnings, line 115)
    FAIL: gcc.dg/Wuse-after-free-2.c  (test for warnings, line 116)

    and comparing tree dumps with a native x86_64-pc-linux-gnu
    run shows a suspicious difference in the "180t.ivopts" dump.
    Indeed -fno-ivopts makes the warning appear for cris-elf
    too.  It was suggested to simply add -fno-ivopts to the
    test-flags, like before -fno-tree-loop-distribute-patterns
    was added; thus.

            PR tree-optimization/108828
            * gcc.dg/Wuse-after-free-2.c: Add -fno-ivopts.

  parent reply	other threads:[~2023-02-28  1:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16 18:31 [Bug tree-optimization/108828] New: " hp at gcc dot gnu.org
2023-02-17  8:03 ` [Bug tree-optimization/108828] " rguenth at gcc dot gnu.org
2023-02-28  1:05 ` cvs-commit at gcc dot gnu.org [this message]
2023-02-28  1:08 ` hp 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-108828-4-JoCKMj0QFQ@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).