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/102690] [11/12/13 regression] g++.dg/warn/Warray-bounds-16.C fails
Date: Thu, 30 Jun 2022 02:15:12 +0000	[thread overview]
Message-ID: <bug-102690-4-2NHblfhRZg@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-102690-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from CVS Commits <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Kito Cheng <kito@gcc.gnu.org>:

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

commit r13-1357-g0f6eef398045deb2a62d18b526831719c7c20c8a
Author: Kito Cheng <kito.cheng@sifive.com>
Date:   Tue Jun 28 18:43:42 2022 +0800

    testsuite/102690: Only check warning for lp64 in Warray-bounds-16.C

    That warning won't happen on ilp32 targets, seems like Andrew Pinski
    already mention that[1] before.

    Verified on riscv32-unknown-elf and riscv64-unknown-elf.

    [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=92879#c1

    gcc/testsuite/ChangeLog:

            PR testsuite/102690
            * g++.dg/warn/Warray-bounds-16.C: XFAIL only on lp64 for the
            warning.

  parent reply	other threads:[~2022-06-30  2:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-11 20:44 [Bug testsuite/102690] New: [12 " seurer at gcc dot gnu.org
2021-10-11 21:02 ` [Bug tree-optimization/102690] " pinskia at gcc dot gnu.org
2021-10-12  6:21 ` rguenth at gcc dot gnu.org
2021-10-12  6:22 ` rguenth at gcc dot gnu.org
2021-11-09  0:56 ` seurer at gcc dot gnu.org
2021-11-09  2:30 ` msebor at gcc dot gnu.org
2021-11-09  8:25 ` [Bug testsuite/102690] [11/12 " rguenth at gcc dot gnu.org
2021-11-10  8:55 ` ebotcazou at gcc dot gnu.org
2021-11-10  9:15 ` rguenth at gcc dot gnu.org
2021-11-10 10:10 ` cvs-commit at gcc dot gnu.org
2021-11-10 10:10 ` cvs-commit at gcc dot gnu.org
2021-11-10 10:11 ` rguenth at gcc dot gnu.org
2021-11-10 11:49 ` ebotcazou at gcc dot gnu.org
2022-04-21  7:50 ` rguenth at gcc dot gnu.org
2022-06-30  2:15 ` cvs-commit at gcc dot gnu.org [this message]
2023-05-29 10:05 ` [Bug testsuite/102690] [11/12/13/14 " jakub 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-102690-4-2NHblfhRZg@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).