public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "seurer at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106120] New: [13 regression] g++.dg/warn/Wstringop-overflow-4.C fails since r13-1268-g8c99e307b20c50
Date: Tue, 28 Jun 2022 16:01:59 +0000	[thread overview]
Message-ID: <bug-106120-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 106120
           Summary: [13 regression] g++.dg/warn/Wstringop-overflow-4.C
                    fails since r13-1268-g8c99e307b20c50
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: other
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:8c99e307b20c502e55c425897fb3884ba8f05882, r13-1268-g8c99e307b20c50
make  -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
dg.exp=g++.dg/warn/Wstringop-overflow-4.C"
FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++98 (test for excess errors)
# of expected passes            59
# of unexpected failures        1


This is for 32 bits on a powerpc64 BE system.


Excess errors:
/home/seurer/gcc/git/gcc-trunk/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:144:3:
warning: 'void* __builtin_memcpy(void*, const void*, unsigned int)' writing 3
bytes into a region of size 0 [-Wstringop-overflow=]


commit 8c99e307b20c502e55c425897fb3884ba8f05882
Author: Aldy Hernandez <aldyh@redhat.com>
Date:   Sat Jun 25 18:58:02 2022 -0400

    Convert DOM to use Ranger rather than EVRP

             reply	other threads:[~2022-06-28 16:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 16:01 seurer at gcc dot gnu.org [this message]
2022-06-28 17:25 ` [Bug other/106120] " aldyh at gcc dot gnu.org
2022-06-28 18:14 ` seurer at gcc dot gnu.org
2022-06-29  0:03 ` hp at gcc dot gnu.org
2022-06-29  9:44 ` [Bug testsuite/106120] " rguenth at gcc dot gnu.org
2022-07-08 23:10 ` hp at gcc dot gnu.org
2022-07-09  6:29 ` aldyh at gcc dot gnu.org
2022-12-14 15:50 ` danglin at gcc dot gnu.org
2022-12-20 14:05 ` rguenth at gcc dot gnu.org
2023-02-10  0:41 ` cvs-commit at gcc dot gnu.org
2023-02-10 18:34 ` hp at gcc dot gnu.org
2023-02-10 18:37 ` seurer at gcc dot gnu.org
2023-02-10 22:52 ` hp at gcc dot gnu.org
2023-11-21 15:21 ` ro at gcc dot gnu.org
2023-11-21 17:54 ` hp at gcc dot gnu.org
2023-11-22  9:09 ` ro at CeBiTec dot Uni-Bielefeld.DE
2023-11-23  0:29 ` cvs-commit 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-106120-4@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).