public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/115345] [12/13/14/15 Regression] Different outputs compared to GCC 11- and MSVC/Clang Date: Tue, 04 Jun 2024 15:10:04 +0000 [thread overview] Message-ID: <bug-115345-4-82BfYHNqmC@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 Jakub Jelinek <jakub at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Last reconfirmed| |2024-06-04 Summary|[12/13/14 REGRESSION] / |[12/13/14/15 Regression] |Different outputs compared |Different outputs compared |to GCC 11- and MSVC/Clang |to GCC 11- and MSVC/Clang Status|UNCONFIRMED |WAITING CC| |jakub at gcc dot gnu.org --- Comment #5 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Please see https://gcc.gnu.org/bugs/ for what we need, we need a self-contained preprocessed testcase, which you haven't provided. You should start by compiling the code with -fsanitize=undefined and/or -fsanitize=address, see if it reports anything, if not, create a minimal self-contained reproducer.
next prev parent reply other threads:[~2024-06-04 15:10 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 ` jakub at gcc dot gnu.org [this message] 2024-06-04 16:33 ` [Bug middle-end/115345] [12/13/14/15 Regression] " 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 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-82BfYHNqmC@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: linkBe 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).