git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pavel Roskin <proski@gnu.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: [PATCH] Remove more gcc extension usage.
Date: Mon, 10 Jul 2006 02:22:03 -0400	[thread overview]
Message-ID: <1152512523.3504.28.camel@dv> (raw)
In-Reply-To: <20060710052255.GA15173@spearce.org>

Hi, Shawn!

On Mon, 2006-07-10 at 01:22 -0400, Shawn Pearce wrote:
>   $ cc -V                                                        
>   cc: Forte Developer 7 C 5.4 2002/03/09
>   usage: cc [ options] files.  Use 'cc -flags' for details
> 
> and from `man cc`:
> 
>   -xc99  enables C99 features:
[skip]
>           o  Flexible Array Members

This must be enabled already because it's used in git (see FLEX_ARRAY).

> So neither of the constructs my patch removes are supported in this
> (old) compiler, although a newer one might accept them with -xc99.
> Yes, I tried building a pristine git-1.4.1 with -xc99.  It barfed,
> as one would expect given the description above.

This means that the Sun compiler has almost all c99 features used by git
with just a little exception (initializers).  I think it's fair that we
fix this incompatibility.  It's very very minor compared to what "gcc
-std=c89 -pedantic" would have required.

-- 
Regards,
Pavel Roskin

  parent reply	other threads:[~2006-07-10  6:22 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-08 18:34 [PATCH] Remove more gcc extension usage Shawn Pearce
2006-07-08 18:51 ` Junio C Hamano
2006-07-08 19:03   ` Shawn Pearce
2006-07-09  7:31     ` Jan-Benedict Glaw
2006-07-10  5:22       ` Shawn Pearce
2006-07-10  6:14         ` Jan-Benedict Glaw
2006-07-10  6:22         ` Pavel Roskin [this message]
2006-07-10  6:25           ` Jan-Benedict Glaw
2006-07-10  6:52             ` Pavel Roskin
2006-07-10  7:35               ` Jan-Benedict Glaw
2006-07-10  8:07                 ` Pavel Roskin
2006-07-10  8:10                   ` Junio C Hamano
2006-07-10  8:18                   ` Jan-Benedict Glaw
2006-07-10  7:47           ` Junio C Hamano
2006-07-12 13:46         ` Paul Jakma

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=1152512523.3504.28.camel@dv \
    --to=proski@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=jbglaw@lug-owl.de \
    --cc=junkio@cox.net \
    --cc=spearce@spearce.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).