Mailing-List: contact harmony-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: harmony-dev@incubator.apache.org
Received-SPF: pass (herse.apache.org: domain of gcjhd-harmony-dev@m.gmane.org
 designates 80.91.229.2 as permitted sender)
To: harmony-dev@incubator.apache.org
From: Egor Pasko <egor.pasko@gmail.com>
Subject: Re: [general] version of GCC...
Date: 03 Nov 2006 18:15:19 +0600
Lines: 26
Message-ID: <ud5847mlk.fsf@gmail.com>
References: <454AC065.8080602@pobox.com> <eifabb$dre$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3
Sender: news <news@sea.gmane.org>

On the 0x216 day of Apache Harmony Gregory Shimansky wrote:
> Geir Magnusson Jr. wrote:
> > did we ever bottom out on what range of GCC we'll support?
> > I have a patch I want to commit that is known to not compile under
> > 4.1.1...
> 
> Hmm no I don't remember such agreement. I think GCC is mostly
> backwards compatible, and anything that compiles on 4.1.1 should
> compile on previous versions. So it is better to support the latest
> stable.
> 
> Not many people would like to install such GCC version, but someone
> like me could at least give warnings that the most recent version of
> GCC doesn't compile some code.

yes, and comment JIRA accordingly (with suggested fix). This way we
can support a very wide renge of GCCs constantly. I doubt I can use
the latest GCC soon, so I cannot check patches constantly.

Does it make sense to use something CruiseControl-ish that walks
around JIRA patches and reports statistics which of them build OK? I
thought of such a tool recently.. Not a task I would dream to
implement though.

-- 
Egor Pasko