public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988
@ 2022-06-30 18:21 seurer at gcc dot gnu.org
  2022-07-01  3:01 ` [Bug testsuite/106149] " pinskia at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: seurer at gcc dot gnu.org @ 2022-06-30 18:21 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 106149
           Summary: [13 regression] g++.dg/warn/Warray-bounds-16.C had
                    bogus errors after r13-1366-g1eef21ccfa5988
           Product: gcc
           Version: 13.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: seurer at gcc dot gnu.org
  Target Milestone: ---

g:1eef21ccfa5988a23a3b71a99613f27ea6a26da6, r13-1366-g1eef21ccfa5988
make  -k check-gcc RUNTESTFLAGS="--target_board=unix'{-m32}'
dg.exp=g++.dg/warn/Warray-bounds-16.C"
FAIL: g++.dg/warn/Warray-bounds-16.C  -std=gnu++98 pr102690 (test for bogus
messages, line 22)
FAIL: g++.dg/warn/Warray-bounds-16.C  -std=gnu++14 pr102690 (test for bogus
messages, line 22)
FAIL: g++.dg/warn/Warray-bounds-16.C  -std=gnu++17 pr102690 (test for bogus
messages, line 22)
FAIL: g++.dg/warn/Warray-bounds-16.C  -std=gnu++20 pr102690 (test for bogus
messages, line 22)
# of expected passes            4
# of unexpected failures        4


I am seeing this only for -m32 test runs.


spawn -ignore SIGHUP
/home/seurer/gcc/git/build/gcc-test/gcc/testsuite/g++/../../xg++
-B/home/seurer/gcc/git/build/gcc-test/gcc/testsuite/g++/../../
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C -m32
-fdiagnostics-plain-output -nostdinc++
-I/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/32/libstdc++-v3/include/powerpc64-unknown-linux-gnu
-I/home/seurer/gcc/git/build/gcc-test/powerpc64-unknown-linux-gnu/32/libstdc++-v3/include
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/libsupc++
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/include/backward
-I/home/seurer/gcc/git/gcc-test/libstdc++-v3/testsuite/util -fmessage-length=0
-std=gnu++98 -O2 -Wall -fdump-tree-optimized -S -o Warray-bounds-16.s
In constructor 'S::S(int)',
    inlined from 'void __static_initialization_and_destruction_0()' at
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C:26:7,
    inlined from '(static initializers for
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C)' at
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C:26:8:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C:22:7:
warning: array subscript [0, 536870911] is outside array bounds of 'void [0]'
[-Warray-bounds]
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/warn/Warray-bounds-16.C:19:51:
note: object of size 0 allocated by 'operator new []'
FAIL: g++.dg/warn/Warray-bounds-16.C  -std=gnu++98 pr102690 (test for bogus
messages, line 22)


commit 1eef21ccfa5988a23a3b71a99613f27ea6a26da6
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jun 28 16:09:21 2022 +0100

    libstdc++: Improve exceptions thrown from fs::temp_directory_path

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug testsuite/106149] [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988
  2022-06-30 18:21 [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988 seurer at gcc dot gnu.org
@ 2022-07-01  3:01 ` pinskia at gcc dot gnu.org
  2022-07-01  6:57 ` rguenth at gcc dot gnu.org
                   ` (3 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: pinskia at gcc dot gnu.org @ 2022-07-01  3:01 UTC (permalink / raw)
  To: gcc-bugs

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

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|libstdc++                   |testsuite

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
Actually I think it is g:0f6eef398045deb2a62d18b526831719c7c20c8a  .

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug testsuite/106149] [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988
  2022-06-30 18:21 [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988 seurer at gcc dot gnu.org
  2022-07-01  3:01 ` [Bug testsuite/106149] " pinskia at gcc dot gnu.org
@ 2022-07-01  6:57 ` rguenth at gcc dot gnu.org
  2022-07-01 10:00 ` kito at gcc dot gnu.org
                   ` (2 subsequent siblings)
  4 siblings, 0 replies; 6+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-07-01  6:57 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|---                         |13.0

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug testsuite/106149] [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988
  2022-06-30 18:21 [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988 seurer at gcc dot gnu.org
  2022-07-01  3:01 ` [Bug testsuite/106149] " pinskia at gcc dot gnu.org
  2022-07-01  6:57 ` rguenth at gcc dot gnu.org
@ 2022-07-01 10:00 ` kito at gcc dot gnu.org
  2022-11-29 18:21 ` rguenth at gcc dot gnu.org
  2022-12-20 14:06 ` rguenth at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: kito at gcc dot gnu.org @ 2022-07-01 10:00 UTC (permalink / raw)
  To: gcc-bugs

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

Kito Cheng <kito at gcc dot gnu.org> changed:

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

--- Comment #2 from Kito Cheng <kito at gcc dot gnu.org> ---
Revert the commit for now...and I am figure out how to resolve this:

lp64 target will have 2 warnings:

22:7: warning: array subscript 0 is outside array bounds of 'void [0]'
[-Warray-bounds]
19:51: note: object of size 0 allocated by 'operator new []'
22:7: warning: 'void* __builtin_memset(void*, int, long unsigned int)' offset
[0, 3] is out of the bounds [0, 0] [-Warray-bounds]

ilp32 target will have only 1 warning:

22:7: warning: array subscript 0 is outside array bounds of 'void [0]'
[-Warray-bounds]
19:51: note: object of size 0 allocated by 'operator new []'

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug testsuite/106149] [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988
  2022-06-30 18:21 [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988 seurer at gcc dot gnu.org
                   ` (2 preceding siblings ...)
  2022-07-01 10:00 ` kito at gcc dot gnu.org
@ 2022-11-29 18:21 ` rguenth at gcc dot gnu.org
  2022-12-20 14:06 ` rguenth at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-11-29 18:21 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Target|powerpc64-linux-gnu         |powerpc64-linux-gnu
                   |                            |i?86-*-*
   Last reconfirmed|                            |2022-11-29
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #3 from Richard Biener <rguenth at gcc dot gnu.org> ---
Confirmed.

^ permalink raw reply	[flat|nested] 6+ messages in thread

* [Bug testsuite/106149] [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988
  2022-06-30 18:21 [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988 seurer at gcc dot gnu.org
                   ` (3 preceding siblings ...)
  2022-11-29 18:21 ` rguenth at gcc dot gnu.org
@ 2022-12-20 14:06 ` rguenth at gcc dot gnu.org
  4 siblings, 0 replies; 6+ messages in thread
From: rguenth at gcc dot gnu.org @ 2022-12-20 14:06 UTC (permalink / raw)
  To: gcc-bugs

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

Richard Biener <rguenth at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
             Status|NEW                         |RESOLVED

--- Comment #4 from Richard Biener <rguenth at gcc dot gnu.org> ---
Fixed by reversion.

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2022-12-20 14:06 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-06-30 18:21 [Bug libstdc++/106149] New: [13 regression] g++.dg/warn/Warray-bounds-16.C had bogus errors after r13-1366-g1eef21ccfa5988 seurer at gcc dot gnu.org
2022-07-01  3:01 ` [Bug testsuite/106149] " pinskia at gcc dot gnu.org
2022-07-01  6:57 ` rguenth at gcc dot gnu.org
2022-07-01 10:00 ` kito at gcc dot gnu.org
2022-11-29 18:21 ` rguenth at gcc dot gnu.org
2022-12-20 14:06 ` rguenth at gcc dot gnu.org

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).