public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Aharon Robbins <arnold@skeeve.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/10025: gcc 3.2.2 recognizes complex functions even without complex.h Date: Wed, 12 Mar 2003 12:26:00 -0000 [thread overview] Message-ID: <20030312122600.12308.qmail@sources.redhat.com> (raw) The following reply was made to PR c/10025; it has been noted by GNATS. From: Aharon Robbins <arnold@skeeve.com> To: arnold@skeeve.com, bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org, gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org Cc: Subject: Re: c/10025: gcc 3.2.2 recognizes complex functions even without complex.h Date: Wed, 12 Mar 2003 14:15:41 +0200 Document it and call it a feature, eh? I think it's a bug; GCC shouldn't talk about conflicts with any builtin function if the header file for it hasn't been included. This is pretty sad. Arnold > Date: 11 Mar 2003 15:07:13 -0000 > To: arnold@skeeve.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, > nobody@gcc.gnu.org > From: bangerth@dealii.org > Reply-To: bangerth@dealii.org, arnold@skeeve.com, gcc-bugs@gcc.gnu.org, > gcc-prs@gcc.gnu.org, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org > Subject: Re: c/10025: gcc 3.2.2 recognizes complex functions even without complex.h > > Synopsis: gcc 3.2.2 recognizes complex functions even without complex.h > > State-Changed-From-To: open->closed > State-Changed-By: bangerth > State-Changed-When: Tue Mar 11 15:07:12 2003 > State-Changed-Why: > This is a gnu extension. The builtin conj function is switched > off if you use -ansi or -std=c89. > > W. > > http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10025
next reply other threads:[~2003-03-12 12:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-03-12 12:26 Aharon Robbins [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-03-12 12:46 Richard Earnshaw 2003-03-11 15:07 bangerth 2003-03-11 9:36 Aharon Robbins
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=20030312122600.12308.qmail@sources.redhat.com \ --to=arnold@skeeve.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).