public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug analyzer/97116] New: Fix argument numbering in C++ member function calls
@ 2020-09-18 14:19 dmalcolm at gcc dot gnu.org
  2020-10-06 21:53 ` [Bug analyzer/97116] " dmalcolm at gcc dot gnu.org
                   ` (4 more replies)
  0 siblings, 5 replies; 6+ messages in thread
From: dmalcolm at gcc dot gnu.org @ 2020-09-18 14:19 UTC (permalink / raw)
  To: gcc-bugs

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

            Bug ID: 97116
           Summary: Fix argument numbering in C++ member function calls
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: analyzer
          Assignee: dmalcolm at gcc dot gnu.org
          Reporter: dmalcolm at gcc dot gnu.org
            Blocks: 97110
  Target Milestone: ---

IIRC -fanalyzer currently misreports parameter numbers in calls when there's an
implicit "this" pointer (e.g. when passing NULL as "this" due to a buggy
allocator to a ctor call it reports "parameter 1", rather than "this").

We might need a langhook for this (but what about LTO, and e.g. mixed-language
analysis?)

(Filing this as part of the -fanalyzer C++ tracker bug)


Referenced Bugs:

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97110
[Bug 97110] [meta-bug] tracker bug for supporting C++ in -fanalyzer

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

end of thread, other threads:[~2020-10-07 13:48 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-09-18 14:19 [Bug analyzer/97116] New: Fix argument numbering in C++ member function calls dmalcolm at gcc dot gnu.org
2020-10-06 21:53 ` [Bug analyzer/97116] " dmalcolm at gcc dot gnu.org
2020-10-06 21:55 ` dmalcolm at gcc dot gnu.org
2020-10-06 21:58 ` dmalcolm at gcc dot gnu.org
2020-10-07 13:40 ` cvs-commit at gcc dot gnu.org
2020-10-07 13:48 ` dmalcolm 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).