public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "djordje.baljozovic at ac dot rwth-aachen.de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/115345] [12/13/14/15 Regression] Different outputs compared to GCC 11- and MSVC/Clang
Date: Thu, 06 Jun 2024 19:18:14 +0000	[thread overview]
Message-ID: <bug-115345-4-iKV8GD8ChO@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-115345-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #15 from Djordje Baljozovic <djordje.baljozovic at ac dot rwth-aachen.de> ---
(In reply to Sam James from comment #14)
> It's worth keeping in mind:
> * Fuzzers are distinct from sanitizers (fuzzers run with random or ~random
> input and often use sanitizers to help find issues)
> * Fuzzers might not be hitting the code you're having trouble with
> * The implementations of sanitizers in gcc vs clang are different (and AFAIK
> oss-fuzz uses clang). They share libsanitizer but when to add
> instrumentation varies.
> * Valgrind can find things that some sanitizers can't.

Hi Sam,
Thanks for this useful information.
To be perfectly honest, I did not even run address/unknown GCC sanitisers as I
thought that Clang and GCC sanitizers are identical (I can confirm that
oss-fuzz uses Clang sanitisers).

Will try Valgrind as I have already detected a share of issues with this
inherited code just by reading it, which did not show up in any
fuzzers'/sanitisers' reports.
Thanks,
George

  parent reply	other threads:[~2024-06-06 19:18 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04 14:32 [Bug c/115345] New: [12/13/14 REGRESSION] / " djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 14:39 ` [Bug c/115345] " djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 14:44 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 14:49 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 14:51 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 15:10 ` [Bug c/115345] [12/13/14/15 Regression] " jakub at gcc dot gnu.org
2024-06-04 16:33 ` [Bug middle-end/115345] " djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 16:48 ` pinskia at gcc dot gnu.org
2024-06-04 16:58 ` jakub at gcc dot gnu.org
2024-06-04 17:03 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 17:11 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-04 18:43 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-05  6:59 ` rguenth at gcc dot gnu.org
2024-06-06 10:57 ` djordje.baljozovic at ac dot rwth-aachen.de
2024-06-06 17:08 ` sjames at gcc dot gnu.org
2024-06-06 19:18 ` djordje.baljozovic at ac dot rwth-aachen.de [this message]
2024-06-27 13:42 ` djordje.baljozovic at ac dot rwth-aachen.de

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-115345-4-iKV8GD8ChO@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).