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 middle-end/112572] [14 regression] LLVM miscompiled since r14-5355-g3cd3a09b3f91a1
Date: Sat, 18 Nov 2023 11:11:00 +0000	[thread overview]
Message-ID: <bug-112572-4-tXfykTcVkM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112572-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #14 from Jakub Jelinek <jakub at gcc dot gnu.org> ---
Try to use optimize (0) attribute or corresponding pragma on some functions in
that file (just those where bad vs. good results in different code generation)
to find out which one is problematic?

  parent reply	other threads:[~2023-11-18 11:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-16 20:06 [Bug middle-end/112572] New: " sjames at gcc dot gnu.org
2023-11-17  0:00 ` [Bug middle-end/112572] " sjames at gcc dot gnu.org
2023-11-17  0:41 ` sjames at gcc dot gnu.org
2023-11-17  4:13 ` sjames at gcc dot gnu.org
2023-11-17  4:14 ` sjames at gcc dot gnu.org
2023-11-17  5:21 ` sjames at gcc dot gnu.org
2023-11-17  5:23 ` pinskia at gcc dot gnu.org
2023-11-17  5:28 ` pinskia at gcc dot gnu.org
2023-11-17 10:43 ` jakub at gcc dot gnu.org
2023-11-18 10:18 ` sjames at gcc dot gnu.org
2023-11-18 10:19 ` sjames at gcc dot gnu.org
2023-11-18 10:23 ` sjames at gcc dot gnu.org
2023-11-18 10:58 ` sjames at gcc dot gnu.org
2023-11-18 10:59 ` sjames at gcc dot gnu.org
2023-11-18 11:00 ` sjames at gcc dot gnu.org
2023-11-18 11:11 ` jakub at gcc dot gnu.org [this message]
2023-11-18 11:36 ` sjames at gcc dot gnu.org
2023-11-18 21:00 ` pinskia at gcc dot gnu.org
2023-11-18 21:13 ` pinskia at gcc dot gnu.org
2023-11-18 21:28 ` pinskia at gcc dot gnu.org
2023-11-18 21:38 ` slyfox at gcc dot gnu.org
2023-11-18 21:55 ` pinskia at gcc dot gnu.org
2023-11-18 22:22 ` pinskia at gcc dot gnu.org
2023-11-18 22:39 ` pinskia at gcc dot gnu.org
2023-11-18 23:06 ` rsandifo at gcc dot gnu.org
2023-11-18 23:39 ` pinskia at gcc dot gnu.org
2023-11-19  7:21 ` pinskia at gcc dot gnu.org
2023-11-19  9:24 ` ebotcazou at gcc dot gnu.org
2023-11-19  9:42 ` sjames at gcc dot gnu.org
2023-11-30 21:09 ` jakub at gcc dot gnu.org
2023-11-30 21:12 ` pinskia at gcc dot gnu.org
2023-11-30 22:29 ` sjames at gcc dot gnu.org
2023-12-04  2:49 ` pinskia at gcc dot gnu.org
2023-12-04 11:01 ` sjames at gcc dot gnu.org
2023-12-06  9:02 ` jakub at gcc dot gnu.org
2023-12-06 18:32 ` 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-112572-4-tXfykTcVkM@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).