public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jamborm at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ipa/112616] [11/12/13/14 Regression] wrong code at -O{s,2,3} on x86_64-linux-gnu since r10-3311
Date: Fri, 05 Jan 2024 15:37:19 +0000 [thread overview]
Message-ID: <bug-112616-4-skOuuoorkb@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112616-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112616
Martin Jambor <jamborm at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|unassigned at gcc dot gnu.org |jamborm at gcc dot gnu.org
Status|NEW |ASSIGNED
--- Comment #5 from Martin Jambor <jamborm at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #2)
> This is like PR 108007 but unlike that one, -fno-tree-dce is not used.
But the patch fixes it, so I gess it's time to make it pass ppc64le bootstrap.
(But I did not want to backport that patch, I wonder whether we can't figure
out something simpler :-/ )
next prev parent reply other threads:[~2024-01-05 15:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-19 5:24 [Bug tree-optimization/112616] New: wrong code at -O{s,2,3} on x86_64-linux-gnu zhendong.su at inf dot ethz.ch
2023-11-19 19:20 ` [Bug tree-optimization/112616] [11/12/13/14 Regression] " pinskia at gcc dot gnu.org
2023-11-19 19:24 ` [Bug ipa/112616] " pinskia at gcc dot gnu.org
2023-11-19 19:25 ` pinskia at gcc dot gnu.org
2023-11-20 9:55 ` rguenth at gcc dot gnu.org
2023-12-07 9:49 ` [Bug ipa/112616] [11/12/13/14 Regression] wrong code at -O{s,2,3} on x86_64-linux-gnu since r10-3311 jakub at gcc dot gnu.org
2024-01-05 15:37 ` jamborm at gcc dot gnu.org [this message]
2024-01-16 12:48 ` jamborm at gcc dot gnu.org
2024-01-24 18:14 ` cvs-commit at gcc dot gnu.org
2024-01-24 19:09 ` jamborm at gcc dot gnu.org
2024-04-08 15:51 ` [Bug ipa/112616] [11/12/13 " cvs-commit at gcc dot gnu.org
2024-05-15 13:46 ` [Bug ipa/112616] [11/12 " 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-112616-4-skOuuoorkb@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).