public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "msebor at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/21433] The COMPONENT_REF case of expand_expr_real_1 is probably wrong Date: Thu, 11 Feb 2021 23:52:47 +0000 [thread overview] Message-ID: <bug-21433-4-kNECEVHgsO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-21433-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=21433 --- Comment #3 from Martin Sebor <msebor at gcc dot gnu.org> --- Created attachment 50171 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50171&action=edit Proposed patch. Patched to remove the CONSTRUCTOR code and replace it with an assert that it doesn't come up. Tested on x86_64-linux.
next prev parent reply other threads:[~2021-02-11 23:52 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-21433-4@http.gcc.gnu.org/bugzilla/> 2021-02-10 23:34 ` msebor at gcc dot gnu.org 2021-02-11 23:52 ` msebor at gcc dot gnu.org [this message] 2021-02-12 0:16 ` msebor at gcc dot gnu.org 2021-05-11 20:00 ` cvs-commit at gcc dot gnu.org 2021-05-11 20:01 ` msebor at gcc dot gnu.org 2005-05-07 3:31 [Bug middle-end/21433] New: " kazu at cs dot umass dot edu 2005-05-07 15:52 ` [Bug middle-end/21433] " pinskia at gcc dot gnu dot 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-21433-4-kNECEVHgsO@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).