public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/31388] ICE building libiberty multilib for mips16 multilibs Date: Thu, 26 Apr 2007 02:30:00 -0000 [thread overview] Message-ID: <20070426022956.2449.qmail@sourceware.org> (raw) In-Reply-To: <bug-31388-622@http.gcc.gnu.org/bugzilla/> ------- Comment #3 from mmitchel at gcc dot gnu dot org 2007-04-26 03:29 ------- Subject: Bug 31388 Author: mmitchel Date: Thu Apr 26 03:29:43 2007 New Revision: 124172 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124172 Log: PR c++/31388 * cp-tree.h (ARITHMETIC_TYPE): Include COMPLEX_TYPE. * typeck.c (type_after_usual_arithmetic_conversions): Adjust, as COMPLEX_TYPE is now an ARITHMETIC_TYPE. * init.c (build_zero_init): Adjust, as COMPLEX_TYPE is now a SCALAR_TYPE. * typeck2.c (digest_init): Allow brace-enclosed initializers for COMPLEX_TYPE, even though that is now a SCALAR_TYPE. PR c++/31388 * g++.dg/ext/complex2.C: New test. Added: trunk/gcc/testsuite/g++.dg/ext/complex2.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/cp-tree.h trunk/gcc/cp/init.c trunk/gcc/cp/typeck.c trunk/gcc/cp/typeck2.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=31388
next prev parent reply other threads:[~2007-04-26 2:30 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-03-29 9:33 [Bug target/31388] New: " nickc at redhat dot com 2007-03-29 10:04 ` [Bug target/31388] " rsandifo at gcc dot gnu dot org 2007-04-01 11:24 ` rsandifo at gcc dot gnu dot org 2007-04-01 11:25 ` rsandifo at gcc dot gnu dot org 2007-04-26 2:30 ` mmitchel at gcc dot gnu dot org [this message] 2007-07-04 17:18 ` mmitchel at gcc dot gnu dot org 2008-02-02 9:45 ` rsandifo at gcc dot gnu dot org 2008-02-02 10:03 ` rsandifo 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=20070426022956.2449.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).