public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/112282] [14 Regression] wrong code (generated code hangs) at -O3 on x86_64-linux-gnu
Date: Mon, 30 Oct 2023 01:53:23 +0000 [thread overview]
Message-ID: <bug-112282-4-4ZiGZAjo7o@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-112282-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112282
--- Comment #6 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Andrew Pinski from comment #5)
> But doing intializing au allows it work. that is:
> struct b au = {};
But I put a `__builtin_trap();` any place where au might be used as
uninitalized, and we don't reach those section of code. So ....
next prev parent reply other threads:[~2023-10-30 1:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-29 22:39 [Bug tree-optimization/112282] New: " zhendong.su at inf dot ethz.ch
2023-10-29 22:41 ` [Bug tree-optimization/112282] [14 Regression] " pinskia at gcc dot gnu.org
2023-10-29 22:51 ` pinskia at gcc dot gnu.org
2023-10-30 0:40 ` sjames at gcc dot gnu.org
2023-10-30 0:41 ` sjames at gcc dot gnu.org
2023-10-30 1:28 ` sjames at gcc dot gnu.org
2023-10-30 1:48 ` pinskia at gcc dot gnu.org
2023-10-30 1:53 ` pinskia at gcc dot gnu.org [this message]
2023-10-30 3:49 ` [Bug tree-optimization/112282] [14 Regression] wrong code (generated code hangs) at -O3 on x86_64-linux-gnu since r14-4777-g88c27070c25309 sjames at gcc dot gnu.org
2023-10-30 9:13 ` tnfchris at gcc dot gnu.org
2023-10-30 14:21 ` rguenth at gcc dot gnu.org
2023-10-30 20:21 ` avieira at gcc dot gnu.org
2023-10-31 9:12 ` avieira at gcc dot gnu.org
2023-10-31 9:12 ` avieira at gcc dot gnu.org
2023-11-14 14:48 ` rguenth at gcc dot gnu.org
2023-11-15 10:36 ` rguenth at gcc dot gnu.org
2023-11-15 10:56 ` rguenth at gcc dot gnu.org
2023-11-15 12:12 ` cvs-commit at gcc dot gnu.org
2023-11-15 12:12 ` rguenth at gcc dot gnu.org
2023-11-16 7:05 ` 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-112282-4-4ZiGZAjo7o@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).