public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/28152]  New: Diagnostic about wrong use _Complex prints __complex__
Date: Sat, 24 Jun 2006 14:14:00 -0000	[thread overview]
Message-ID: <bug-28152-280@http.gcc.gnu.org/bugzilla/> (raw)

$ cat t.c
int
main (void)
{
  _Complex float z;

  z = _Complex (1.90000007326203904e+19, 0.0);
  z = _Complex (1.0e+0, 0.0) / z;
$ ./cc1 -quiet t.c
t.c: In function 'main':
t.c:6: error: expected expression before '__complex__'
t.c:7: error: expected expression before '__complex__'
$ ./cc1 --version
GNU C version 4.2.0 20060624 (experimental) (x86_64-unknown-linux-gnu)
        compiled by GNU C version 4.0.2 20050901 (prerelease) (SUSE Linux).
GGC heuristics: --param ggc-min-expand=30 --param ggc-min-heapsize=4096
$


-- 
           Summary: Diagnostic about wrong use _Complex prints __complex__
           Product: gcc
           Version: 4.2.0
            Status: UNCONFIRMED
          Keywords: diagnostic
          Severity: normal
          Priority: P3
         Component: c
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: steven at gcc dot gnu dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28152


             reply	other threads:[~2006-06-24 14:01 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-24 14:14 steven at gcc dot gnu dot org [this message]
2006-06-28 21:21 ` [Bug c/28152] " pinskia at gcc dot gnu dot org
2006-06-28 22:00 ` pinskia at gcc dot gnu dot org
2006-07-02 16:03 ` gdr at integrable-solutions dot net
2006-07-02 16:11 ` pinskia at gcc dot gnu dot org
2006-07-02 16:37 ` gdr at integrable-solutions dot net
2008-08-14 13:04 ` manu at gcc dot gnu dot org
2008-08-14 13:09 ` [Bug c++/28152] " manu at gcc dot gnu dot org
2009-02-07 20:54 ` manu at gcc dot gnu dot org
2009-05-04 12:48 ` manu at gcc dot gnu dot org
2009-05-04 12:50 ` manu 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-28152-280@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: link
Be 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).