git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Martijn Kuipers <martijn.kuipers@gmail.com>
To: Antti-Juhani Kaijanaho <antti-juhani@kaijanaho.info>
Cc: Linus Torvalds <torvalds@osdl.org>,
	Jason Riedy <ejr@EECS.Berkeley.EDU>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] Spell __attribute__ correctly in cache.h.
Date: Mon, 29 Aug 2005 09:55:22 +0100	[thread overview]
Message-ID: <4312CD7A.4010401@gmail.com> (raw)
In-Reply-To: <4312C8D6.9010200@kaijanaho.info>

Sorry, I am not very familiar with all those command line options:
Anyway, redo was easy:
with: --std=c9x

gcc-2.95 --std=c9x -pedantic -Wall -W -ofoo foo.c
foo.c:5: field `b' has incomplete type
foo.c: In function `main':
foo.c:20: warning: unknown conversion type character `z' in format
foo.c:20: warning: unknown conversion type character `z' in format
foo.c:20: warning: unknown conversion type character `z' in format
foo.c:20: warning: too many arguments for format

I found one man-page online 
(http://gcc.gnu.org/onlinedocs/gcc-2.95.3/gcc_2.html#SEC3), which seemed 
to suggest -fstd=c9x (if I understood correclty). This gave the same 
results.

I hope this makes it a bit more useful :-)
If not, just let me know.

Kind regards,
Martijn


Antti-Juhani Kaijanaho wrote:

>Martijn Kuipers wrote:
>  
>
>>martijn@hobbes:~$ gcc-2.95 --std=c99 -pedantic -Wall -W -ofoo foo.c
>>cc1: unknown C standard `c99'
>>    
>>
>
>This makes this test a little less useful.  Try with --std=c9x (GCC 2.95
>is old enough not to know the standard by the "official" name).
>
>According to GCC 3.0 C99 status page [1], 3.0 supported flexible array
>members.  There is no similar page for 2.95.
>
>  
>

      reply	other threads:[~2005-08-29  8:55 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-19  4:10 [PATCH] Spell __attribute__ correctly in cache.h Jason Riedy
2005-08-19  9:04 ` Junio C Hamano
2005-08-19 14:58   ` Jason Riedy
2005-08-19 19:53     ` Junio C Hamano
2005-08-23 21:20       ` Jason Riedy
2005-08-28 10:14         ` Junio C Hamano
2005-08-28 17:11           ` Jason Riedy
2005-08-28 17:46             ` Linus Torvalds
2005-08-28 19:08               ` Antti-Juhani Kaijanaho
2005-08-28 19:48                 ` Linus Torvalds
2005-08-29  8:17                   ` Martijn Kuipers
2005-08-29  8:35                     ` Antti-Juhani Kaijanaho
2005-08-29  8:55                       ` Martijn Kuipers [this message]

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=4312CD7A.4010401@gmail.com \
    --to=martijn.kuipers@gmail.com \
    --cc=antti-juhani@kaijanaho.info \
    --cc=ejr@EECS.Berkeley.EDU \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=torvalds@osdl.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 NNTP newsgroup(s).