public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hp at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/106120] [13 regression] g++.dg/warn/Wstringop-overflow-4.C fails since r13-1268-g8c99e307b20c50
Date: Wed, 29 Jun 2022 00:03:20 +0000	[thread overview]
Message-ID: <bug-106120-4-hfJm0oaCjJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-106120-4@http.gcc.gnu.org/bugzilla/>

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

Hans-Peter Nilsson <hp at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |hp at gcc dot gnu.org

--- Comment #3 from Hans-Peter Nilsson <hp at gcc dot gnu.org> ---
(In reply to seurer from comment #2)
> I am not sure.  This only happens for 32 bit runs on power.  64 bit ones
> work fine.

You mean something like -m32 with powerpc64-linux-gnu?

I'll dump my observations for cris-elf (a "32-bit target") hoping it'll help:
At r13-1268-g8c99e307b20c50:

Running TOPLEVEL/gcc/testsuite/g++.dg/dg.exp ...
...
FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++98 (test for excess errors)
...

At r13-1333-g74956337e827, (long) after r13-1271-g80ace9185dc534
aldyh@redhat.com "XFAIL a test in g++.dg/warn/Wstringop-overflow-4.C":

Running TOPLEVEL/gcc/testsuite/g++.dg/dg.exp ...
FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++98 (test for excess errors)
XPASS: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++14  (test for bogus
messages, line 198)
XPASS: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++17  (test for bogus
messages, line 198)
XPASS: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++20  (test for bogus
messages, line 198)

g++.log at that latter commit:
FAIL: g++.dg/warn/Wstringop-overflow-4.C  -std=gnu++98 (test for excess errors)
Excess errors:
TOPLEVEL/gcc/testsuite/g++.dg/warn/Wstringop-overflow-4.C:144:3: warning:
'void* __builtin_memcpy(void*, const void*, long unsigned int)' writing 3 bytes
into a region of size 0 [-Wstringop-overflow=]

  parent reply	other threads:[~2022-06-29  0:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-28 16:01 [Bug other/106120] New: " seurer at gcc dot gnu.org
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 [this message]
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-hfJm0oaCjJ@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).