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 testsuite/101517] Some testcases were lost when tree-ssa was merged
Date: Fri, 30 Jul 2021 17:32:01 +0000	[thread overview]
Message-ID: <bug-101517-4-kroxBup8Bh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-101517-4@http.gcc.gnu.org/bugzilla/>

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

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

https://gcc.gnu.org/g:d68d275a00573be49f5e83eba52ce3f26d11db9e

commit r12-2632-gd68d275a00573be49f5e83eba52ce3f26d11db9e
Author: Andrew Pinski <apinski@marvell.com>
Date:   Thu Jul 29 12:56:18 2021 -0700

    Add testcases that got lost when tree-ssa was merged

    So I was looking at some older PRs (PR 16016 in this case),
    I noticed that some of the testcases were removed when
    the tree-ssa branch was merged. This adds them back in.

    OK? Bootstrapped and tested on x86_64-linux-gnu with no regressions.

    Thanks,
    Andrew Pinski

    gcc/testsuite/ChangeLog:

            PR testsuite/101517
            * g++.dg/warn/Wunused-18.C: New test.
            * gcc.c-torture/compile/20030405-2.c: New test.
            * gcc.c-torture/compile/20040304-2.c: New test.
            * gcc.dg/20030612-2.c: New test.

  parent reply	other threads:[~2021-07-30 17:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19 19:06 [Bug testsuite/101517] New: " pinskia at gcc dot gnu.org
2021-07-19 19:08 ` [Bug testsuite/101517] " pinskia at gcc dot gnu.org
2021-07-29 18:35 ` pinskia at gcc dot gnu.org
2021-07-29 20:34 ` pinskia at gcc dot gnu.org
2021-07-30 17:32 ` cvs-commit at gcc dot gnu.org [this message]
2021-07-30 17:39 ` 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-101517-4-kroxBup8Bh@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).