This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug target/32187] Complex __float128 is rejected
- From: "gdr at cs dot tamu dot edu" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 2 Jun 2007 20:28:48 -0000
- Subject: [Bug target/32187] Complex __float128 is rejected
- References: <bug-32187-10259@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #3 from gdr at cs dot tamu dot edu 2007-06-02 20:28 -------
Subject: Re: Complex __float128 is rejected
"joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org> writes:
| Subject: Re: Complex __float128 is rejected
|
| On Sat, 2 Jun 2007, ubizjak at gmail dot com wrote:
|
| > Is this a parser problem? Compilation fails even for generic:
| >
| > --cut here--
| > typedef float DFtype __attribute__((mode(DF)));
| >
| > __complex__ DFtype z;
|
| Of course, 6.7.2 paragraph 2 does not include _Complex typedef-name in the
| possible sets of type specifiers.
Out of curiosity, do you happen to know why typedefs to floating point
types should be disallowed?
-- Gaby
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32187