[Bug c++/28152] Diagnostic about wrong use _Complex prints __complex__

2009-05-04 Thread manu at gcc dot gnu dot org
--- Comment #10 from manu at gcc dot gnu dot org 2009-05-04 12:49 --- FIXED in GCC 4.5 -- manu at gcc dot gnu dot org changed: What|Removed |Added Status|NEW

[Bug c++/28152] Diagnostic about wrong use _Complex prints __complex__

2009-05-04 Thread manu at gcc dot gnu dot org
--- Comment #9 from manu at gcc dot gnu dot org 2009-05-04 12:48 --- Subject: Bug 28152 Author: manu Date: Mon May 4 12:47:53 2009 New Revision: 147097 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=147097 Log: 2009-05-04 Manuel Lopez-Ibanez PR c++/28152 cp/

[Bug c++/28152] Diagnostic about wrong use _Complex prints __complex__

2009-02-07 Thread manu at gcc dot gnu dot org
--- Comment #8 from manu at gcc dot gnu dot org 2009-02-07 20:54 --- Patch here: http://gcc.gnu.org/ml/gcc-patches/2008-10/msg00874.html -- manu at gcc dot gnu dot org changed: What|Removed |Added --

[Bug c++/28152] Diagnostic about wrong use _Complex prints __complex__

2008-08-14 Thread manu at gcc dot gnu dot org
--- Comment #7 from manu at gcc dot gnu dot org 2008-08-14 13:07 --- This is FIXED for C but not for C++. Probably this is the same bug as 14875 but just in case, I keep open both. -- manu at gcc dot gnu dot org changed: What|Removed |Added ---

[Bug c/28152] Diagnostic about wrong use _Complex prints __complex__

2008-08-14 Thread manu at gcc dot gnu dot org
--- Comment #6 from manu at gcc dot gnu dot org 2008-08-14 13:03 --- Subject: Bug 28152 Author: manu Date: Thu Aug 14 13:01:58 2008 New Revision: 139097 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=139097 Log: 2008-08-08 Manuel Lopez-Ibanez <[EMAIL PROTECTED]> PR c/

[Bug c/28152] Diagnostic about wrong use _Complex prints __complex__

2006-07-02 Thread gdr at integrable-solutions dot net
--- Comment #5 from gdr at integrable-solutions dot net 2006-07-02 16:37 --- Subject: Re: Diagnostic about wrong use _Complex prints __complex__ "pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: | (In reply to comment #3) | > Indeed. However, we can approximate a fix by te

[Bug c/28152] Diagnostic about wrong use _Complex prints __complex__

2006-07-02 Thread pinskia at gcc dot gnu dot org
--- Comment #4 from pinskia at gcc dot gnu dot org 2006-07-02 16:11 --- (In reply to comment #3) > Indeed. However, we can approximate a fix by testing whether we're > compiling under C99, GNU99, or just C90, or C++. That would not work as _Complex is accepted in GNU90 more and with the

[Bug c/28152] Diagnostic about wrong use _Complex prints __complex__

2006-07-02 Thread gdr at integrable-solutions dot net
--- Comment #3 from gdr at integrable-solutions dot net 2006-07-02 16:03 --- Subject: Re: Diagnostic about wrong use _Complex prints __complex__ "pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes: | Confirmed, we don't record in the preprocessor which keyword is | used, _Com

[Bug c/28152] Diagnostic about wrong use _Complex prints __complex__

2006-06-28 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-06-28 21:21 --- PR 14875 is the related bug. -- pinskia at gcc dot gnu dot org changed: What|Removed |Added BugsT

[Bug c/28152] Diagnostic about wrong use _Complex prints __complex__

2006-06-28 Thread pinskia at gcc dot gnu dot org
--- Comment #1 from pinskia at gcc dot gnu dot org 2006-06-28 21:18 --- Confirmed, we don't record in the preprocessor which keyword is used, _Complex is treated the same as __complex__. There is another bug about a similar issue with "or" and |. -- pinskia at gcc dot gnu dot org ch