Bug 96014 - [11 regression] g++.dg/analyzer/pr94028.C excess errors starting with r11-1697
Summary: [11 regression] g++.dg/analyzer/pr94028.C excess errors starting with r11-1697
Status: RESOLVED FIXED
Alias: None
Product: gcc
Classification: Unclassified
Component: testsuite (show other bugs)
Version: 11.0
: P3 normal
Target Milestone: 11.0
Assignee: Jonathan Wakely
URL:
Keywords: diagnostic
Depends on:
Blocks:
 
Reported: 2020-06-30 22:18 UTC by Bill Seurer
Modified: 2020-07-16 20:24 UTC (History)
1 user (show)

See Also:
Host: powerpc64*-linux-gnu
Target: powerpc64*-linux-gnu
Build: powerpc64*-linux-gnu
Known to work:
Known to fail:
Last reconfirmed: 2020-07-01 00:00:00


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Bill Seurer 2020-06-30 22:18:13 UTC
g:75ff24e1920ea6b198350a2961e23175e6108e75, r11-1697 

make -k check-gcc RUNTESTFLAGS=analyzer.exp=g++.dg/analyzer/pr94028.C

FAIL: g++.dg/analyzer/pr94028.C  -std=c++98 (test for excess errors)
FAIL: g++.dg/analyzer/pr94028.C  -std=c++14 (test for excess errors)
FAIL: g++.dg/analyzer/pr94028.C  -std=c++17 (test for excess errors)
FAIL: g++.dg/analyzer/pr94028.C  -std=c++2a (test for excess errors)

Excess errors:
/home/seurer/gcc/git/gcc-test/gcc/testsuite/g++.dg/analyzer/pr94028.C:28:21: warning: use of possibly-NULL '<unknown>' where non-null expected [CWE-690] [-Wanalyzer-possible-null-argument]
Comment 1 Bill Seurer 2020-06-30 23:34:04 UTC
Also these failures:

FAIL: g++.dg/cpp1y/lambda-generic-69078-1.C  -std=gnu++14 (test for excess errors)
FAIL: g++.dg/cpp1y/lambda-generic-69078-1.C  -std=gnu++17 (test for excess errors)
FAIL: g++.dg/cpp1y/lambda-generic-69078-1.C  -std=gnu++2a (test for excess errors)
Comment 2 Martin Sebor 2020-07-01 00:11:52 UTC
The failures are also discussed here:
  https://gcc.gnu.org/pipermail/gcc-patches/2020-June/549179.html

The g++.dg/analyzer/pr94028.C failure needs an adjustment to the test.

The g++.dg/cpp1y/lambda-generic-69078-1.C ICE was reported in pr96008, a duplicate of pr95984, and needs changes to the C++ front end.
Comment 3 Martin Sebor 2020-07-01 00:15:17 UTC
Let me fix up the analyzer test.
Comment 4 Jonathan Wakely 2020-07-01 09:54:40 UTC
I already sent a patch for g++.dg/analyzer/pr94028.C

https://gcc.gnu.org/pipermail/gcc-patches/2020-June/549202.html
Comment 5 Martin Sebor 2020-07-01 14:53:45 UTC
Reassigning to Jon per comment #4.
Comment 6 GCC Commits 2020-07-01 19:21:54 UTC
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:039a630d787dc18c76b81f08a322ba1e0d91082d

commit r11-1769-g039a630d787dc18c76b81f08a322ba1e0d91082d
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Tue Jun 30 17:40:08 2020 +0100

    analyzer: Fix -Wanalyzer-possible-null-argument warning (PR 96014)
    
    gcc/testsuite/ChangeLog:
    
            PR testsuite/96014
            * g++.dg/analyzer/pr94028.C: Make operator new non-throwing so
            that the compiler doesn't implicitly mark it as returning
            non-null.
Comment 7 Jonathan Wakely 2020-07-01 20:48:50 UTC
.
Comment 8 GCC Commits 2020-07-16 20:24:46 UTC
The master branch has been updated by Jonathan Wakely <redi@gcc.gnu.org>:

https://gcc.gnu.org/g:75edc31f9ebe7f8b933860981a124f7f0993214b

commit r11-2182-g75edc31f9ebe7f8b933860981a124f7f0993214b
Author: Jonathan Wakely <jwakely@redhat.com>
Date:   Thu Jul 16 11:44:32 2020 +0100

    analyzer: Use noexcept instead of throw() for C++11 and later (PR 96014)
    
    gcc/testsuite/ChangeLog:
    
            PR testsuite/96014
            * g++.dg/analyzer/pr94028.C: Replace dynamic exception
            specification with noexcept-specifier for C++11 and later.