public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Aharon Robbins <arnold@skeeve.com>
To: gcc-gnats@gcc.gnu.org
Subject: c/10025: gcc 3.2.2 recognizes complex functions even without complex.h
Date: Tue, 11 Mar 2003 09:36:00 -0000	[thread overview]
Message-ID: <200303110930.h2B9Uu45008121@localhost.localdomain> (raw)


>Number:         10025
>Category:       c
>Synopsis:       gcc 3.2.2 recognizes complex functions even without complex.h
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          rejects-legal
>Submitter-Id:   net
>Arrival-Date:   Tue Mar 11 09:36:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     Arnold Robbins
>Release:        3.2.2
>Organization:
Pioneer Consulting Ltd.
>Environment:
System: Linux aahz 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux
Architecture: i686

	
host: i686-pc-linux-gnu
build: i686-pc-linux-gnu
target: i686-pc-linux-gnu
configured with: ./configure --prefix=/usr/gcc3
>Description:
	GCC recognizes the `conj' function and complains about it, even if NO headers
	are included.
>How-To-Repeat:
	int conj(a)
	int a;
	{
		return a;
	}

	main()
	{
		printf("%d\n", conj(1));
	}

	/* Note: NO header files included. Error message is:
	 * foo.c:2: warning: conflicting types for built-in function `conj'
	 */
>Fix:
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-03-11  9:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-11  9:36 Aharon Robbins [this message]
2003-03-11 15:07 bangerth
2003-03-12 12:26 Aharon Robbins
2003-03-12 12:46 Richard Earnshaw

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=200303110930.h2B9Uu45008121@localhost.localdomain \
    --to=arnold@skeeve.com \
    --cc=gcc-gnats@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).