public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/42760] [4.4 Regression] ICE in convert_move Date: Fri, 15 Jan 2010 16:24:00 -0000 [thread overview] Message-ID: <20100115162356.24856.qmail@sourceware.org> (raw) In-Reply-To: <bug-42760-87@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from rguenth at gcc dot gnu dot org 2010-01-15 16:23 ------- Trunk has if (COMPLEX_MODE_P (TYPE_MODE (TREE_TYPE (from)))) instead of the 4.4 if (TREE_CODE (TREE_TYPE (from)) == COMPLEX_TYPE) Fixed by 2009-06-17 Steve Ellcey <sje@cup.hp.com> * expr.c (expand_assignment): Change complex type check. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42760
next prev parent reply other threads:[~2010-01-15 16:24 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-01-15 15:48 [Bug middle-end/42760] New: " jakub at gcc dot gnu dot org 2010-01-15 16:10 ` [Bug middle-end/42760] " jakub at gcc dot gnu dot org 2010-01-15 16:24 ` rguenth at gcc dot gnu dot org [this message] 2010-01-15 17:02 ` jakub at gcc dot gnu dot org 2010-01-16 9:45 ` jakub at gcc dot gnu dot org 2010-01-16 9:46 ` jakub at gcc dot gnu dot org 2010-01-16 15:24 ` jakub 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=20100115162356.24856.qmail@sourceware.org \ --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).