public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ro at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug analyzer/111475] Many C++ analyzer tests FAIL
Date: Fri, 19 Jan 2024 10:10:14 +0000	[thread overview]
Message-ID: <bug-111475-4-4SAdnE3AIG@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-111475-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #3 from Rainer Orth <ro at gcc dot gnu.org> ---
I've now reduced c-c++-common/analyzer/allocation-size-1.c:test_2 to minimal
preprocessed the inputs, still showing the difference:

$ cc1plus -fpreprocessed as1-sol2.ii -quiet -std=c++98
-fdiagnostics-color=never -fno-diagnostics-show-caret
-fno-diagnostics-show-line-numbers -fdiagnostics-urls=never
-fdiagnostics-path-format=separate-events -fdiagnostics-text-art-charset=none
-fmessage-length=0 -fanalyzer -fanalyzer-call-summaries -o as1.s

* as1-sol2.ii:

as1-sol2.ii:17:37: note: (1) allocated 42 bytes and assigned to ‘int32_t*’ {aka
‘int*’} here; ‘sizeof (int32_t {aka int})’ is ‘4’

* as1-lx.ii:

as1-lx.ii:21:37: note: (1) allocated 42 bytes here
as1-lx.ii:21:37: note: (2) assigned to ‘int32_t*’ {aka ‘int*’} here; ‘sizeof
(int32_t {aka int})’ is ‘4’

  parent reply	other threads:[~2024-01-19 10:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-19 11:50 [Bug analyzer/111475] New: " ro at gcc dot gnu.org
2023-09-19 11:51 ` [Bug analyzer/111475] " ro at gcc dot gnu.org
2024-01-18 12:52 ` ro at gcc dot gnu.org
2024-01-18 15:16 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-01-19 10:10 ` ro at gcc dot gnu.org [this message]
2024-01-19 10:11 ` ro at gcc dot gnu.org
2024-01-19 10:11 ` ro at gcc dot gnu.org
2024-04-23 13:46 ` [Bug analyzer/111475] [14 regression] " ro at gcc dot gnu.org
2024-04-23 17:16 ` ro at gcc dot gnu.org
2024-04-26 13:06 ` [Bug analyzer/111475] [14/15 " ro at gcc dot gnu.org
2024-04-26 13:15 ` dmalcolm at gcc dot gnu.org
2024-04-26 13:36 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-04-30 19:43 ` dmalcolm at gcc dot gnu.org
2024-05-01 10:29 ` ro at CeBiTec dot Uni-Bielefeld.DE
2024-05-03 13:12 ` cvs-commit at gcc dot gnu.org
2024-05-03 13:34 ` [Bug analyzer/111475] [14 " dmalcolm at gcc dot gnu.org
2024-05-06  8:55 ` 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-111475-4-4SAdnE3AIG@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).