public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "neil at daikokuya dot co dot uk" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/11459] -stdc=c99 -pedantic -ansi warns about C90's non long-long support when in C99 mode
Date: Wed, 09 Jul 2003 05:45:00 -0000	[thread overview]
Message-ID: <20030709054506.15847.qmail@sources.redhat.com> (raw)
In-Reply-To: <20030708045637.11459.debian-gcc@lists.debian.org>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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



------- Additional Comments From neil at daikokuya dot co dot uk  2003-07-09 05:45 -------
Subject: Re:  -stdc=c90 -pedantic -ansi warns about C90's non long-long support when in C99 mode

pinskia at physics dot uc dot edu wrote:-

> pinskia at physics dot uc dot edu changed:
> 
>            What    |Removed                     |Added
> ----------------------------------------------------------------------------
>             Summary|-stdc=c90 -pedantic warns   |-stdc=c90 -pedantic -ansi
>                    |about C90's non long-long   |warns about C90's non long-
>                    |support when in C99 mode    |long support when in C99
>                    |                            |mode
> 
> 
> ------- Additional Comments From pinskia at physics dot uc dot edu  2003-07-08 20:11 -------
> The bug report is wrong because with those options, I do not get the warning but reading 
> the bug report which is this is forward from, I see that the option -ansi is there, I do not 
> know what is should happen when you say '-std=c99 -ansi' or '-ansi -std=c99', should gcc 
> put into c89 or c99?  Could some else look at this bug and say what should gcc do?

-ansi means -std=c89.  Which ever comes later of -ansi and -std=c99 should win; this
is the general rule (sadly some exceptions are insisted on).

Neil.


  parent reply	other threads:[~2003-07-09  5:45 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-08  4:56 [Bug c/11459] New: -stdc=c90 -pedantic " debian-gcc at lists dot debian dot org
2003-07-08 20:11 ` [Bug c/11459] -stdc=c90 -pedantic -ansi " pinskia at physics dot uc dot edu
2003-07-09  5:44   ` Neil Booth
2003-07-08 23:57 ` [Bug c/11459] -stdc=c99 " neroden at gcc dot gnu dot org
2003-07-09  5:45 ` neil at daikokuya dot co dot uk [this message]
2003-07-09  7:27 ` neroden at gcc dot gnu dot org
2003-07-09  7:28 ` [Bug c/11459] -ansi -std=c99 -pedantic " neroden at gcc dot gnu dot org
2003-08-23  0:15 ` dhazeghi at yahoo dot com
2003-10-24 18:11 ` dhazeghi at yahoo dot com
2004-09-25 18:23 ` pinskia at gcc dot gnu dot org
2004-09-26  0:59 ` cvs-commit at gcc dot gnu dot org
2004-09-26  1:02 ` pinskia at gcc dot gnu dot org
2005-05-01 10:34 ` cvs-commit at gcc dot gnu dot org
2005-05-01 11:00 ` jsm28 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=20030709054506.15847.qmail@sources.redhat.com \
    --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).