public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/107196] [13 Regression] llvm-14.0.6 is miscompiles by gcc-13 in -O3: hangs llvm testsuite (inliner seems to break it)
Date: Sun, 09 Oct 2022 19:25:33 +0000	[thread overview]
Message-ID: <bug-107196-4-gr3sLWXwOc@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-107196-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #5 from Sergei Trofimovich <slyfox at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #1)
> We definitely needs more information than this. It could very well be a bug
> in LLVM too.
> Have you tried compiling LLVM with -fsanitize=address ?

(In reply to Andrew Pinski from comment #2)
> How about -fwrapv ?

Tried the following:
- -fwrapv: no change, hangup still happens
- -fsanitize=address: hangup disappears, no reports on stderr
- -fwrapv -fsanitize=address: hangup disappears, no reports on stderr
- -fsanitize=undefined: hangup disappears, no reports on stderr

  parent reply	other threads:[~2022-10-09 19:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-09 18:32 [Bug ipa/107196] New: " slyfox at gcc dot gnu.org
2022-10-09 18:34 ` [Bug ipa/107196] " pinskia at gcc dot gnu.org
2022-10-09 18:34 ` pinskia at gcc dot gnu.org
2022-10-09 18:38 ` slyfox at gcc dot gnu.org
2022-10-09 18:47 ` pinskia at gcc dot gnu.org
2022-10-09 19:25 ` slyfox at gcc dot gnu.org [this message]
2022-10-09 20:02 ` slyfox at gcc dot gnu.org
2022-10-10  7:25 ` rguenth at gcc dot gnu.org
2022-10-20 17:28 ` pinskia at gcc dot gnu.org
2022-10-21  6:26 ` slyfox at gcc dot gnu.org
2022-10-21  6:28 ` pinskia 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-107196-4-gr3sLWXwOc@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).