No subject

Tue Nov 2 11:10:42 EDT 2010

performance, we moved to gcc4 many years ago because the gcc4 compiler
produced so much better performance.

My opinion is that there are two comminutes that we should focus on: 1) ITK
users who are software/algorithm developers, 2) medical image processing en=
d
users who prefer pre-built binaries.

Group #1 is mostly using a fairly recent freely available version of
compilers for their platforms.  The ITK dashboard has many compilers that
are only used for testing, but never really used by end users.  I'd contend
that if there is a user community that depends on Mac 10.3.9 (released in
April 15, 2005).  That communities need for ITKv4 is not large enough to
justify the effort of maintaining it.  Even RedHat EL4 (4.1, also known as
Update 1, 2005-06-09) has gccv4, and RedHat is one of the most conservative
Linux variations.

Group #2 depends on Group #1 to get them the best compiled version of the
library.

In my highly opinionated cost/benefit analysis, we will gain more happy
end-users from targeted performance testing and maintenance simplifications
at the cost of a few un-happy end-users who will be required to find a way
to install an updated free (from a licensing perspective) one of our few
supported compilers.

For ITKv4's life cycle of September 2011-2020, we should target the
"available commodity" compilers of the most commonly used operating systems
of say 2009.

That would be
WindowsXP -- (released in November 2007) Visual Studio 2008 Express ,
Mac 10.5 (October 26, 2007)-- gcc4
RedHat Linux 5 (5.1, also known as Update 1, 2007-11-07)--gcc4

=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
So in summary:
** ITKv4 won't be "in the wild" until about a year from now.
** Now is our only opportunity to simplify the maintenance burden for the
next 10 years (i.e. old compilers not being supported).
** The diversity of compilers to be supported in ITKv4 will be monotonicall=
y
increasing over the next 10 years.

Regards,
Hans
--=20
Hans J. Johnson, Ph.D.
Hans-johnson at uiowa.edu

278 GH
The University of Iowa
Iowa City, IA 52241
(319) 353 8587

> From: Bill Lorensen <bill.lorensen at gmail.com>
> Date: Wed, 8 Dec 2010 10:08:54 -0500
> To: Hans Johnson <hans-johnson at uiowa.edu>
> Cc: Brad King <brad.king at kitware.com>, ITK <insight-developers at itk.org>
> Subject: Re: [Insight-developers] vxl update
>=20
> I don't think we should drop gcc 3.x. For example, my mingw gcc
> compiler is 3.4.5 and builds ITK just fine. It is a recent download of
> mingw.
>=20
> I'm sure there are a lot of folks out there still using gcc 3.x
>=20
>=20
>=20
> On Wed, Dec 8, 2010 at 9:49 AM, Hans Johnson <hans-johnson at uiowa.edu> wro=
te:
>> Food for thought:
>>=20
>> If we just stick to gcc 4.0 or greater, then we reduce the spread of
>> supported features sets in compilers.
>>=20
>> On mac from two OS revisions ago (i.e. 10.4 and latest is 10.6) gcc4 is
>> available by default.
>>=20
>> On Linux RedHad EL4 a two OS revisions ago is also a default compiler on
>> that platform.
>>=20
>> Hans
>>=20
>> --
>> Hans J. Johnson, Ph.D.
>> Hans-johnson at uiowa.edu
>>=20
>> 278 GH
>> The University of Iowa
>> Iowa City, IA 52241
>> (319) 353 8587
>>=20
>>=20
>>> From: Brad King <brad.king at kitware.com>
>>> Date: Wed, 08 Dec 2010 09:27:01 -0500
>>> To: ITK <insight-developers at itk.org>
>>> Subject: Re: [Insight-developers] vxl update
>>>=20
>>> On 12/07/2010 06:19 PM, Sean McBride wrote:
>>>> On Tue, 7 Dec 2010 17:54:40 -0500, Bill Lorensen said:
>>>>> There are a few issues. Several platforms have compiler errors:
>>>=20
>>> Thanks for the summary.
>>>=20
>>>>> http://www.cdash.org/CDash/viewBuildError.php?buildid=3D795777
>>>> Personally, I'd ditch gcc 3.3. =A0If it's running OS 10.4, gcc 4.0 is al=
so
>>>> available there.
>>>=20
>>> I agree. =A0Any objections to dropping gcc 3.3 and this midworld dashboar=
d?
>>>=20
>>>>> http://www.cdash.org/CDash/viewBuildError.php?buildid=3D795403
>>>> I could fix this the same way it was fixed for VTK/ITK years ago: an #=
if
>>>> APPLE that ignores the try-compile results.
>>>=20
>>> http://itk.org/gitweb?p=3DITK.git;a=3Dcommitdiff;h=3D2d832c34
>>>=20
>>>>> http://www.cdash.org/CDash/viewBuildError.php?buildid=3D795260
>>>>> http://www.cdash.org/CDash/viewBuildError.php?buildid=3D795348
>>>>=20
>>>> These are hitting an #error...
>>>=20
>>> http://itk.org/gitweb?p=3DITK.git;a=3Dcommitdiff;h=3D388ab9f1
>>> http://itk.org/gitweb?p=3DITK.git;a=3Dcommitdiff;h=3Dd09fc7b5
>>>=20
>>>> http://www.cdash.org/CDash/testSummary.php?project=3D2&name=3Dtest_pow_log=
&date
>>>> =3D2
>>>> 010-12-07
>>>=20
>>> http://itk.org/gitweb?p=3DITK.git;a=3Dcommitdiff;h=3Dd280635a
>>>=20
>>> -Brad
>>> _______________________________________________
>>> Powered by www.kitware.com
>>>=20
>>> Visit other Kitware open-source projects at
>>> http://www.kitware.com/opensource/opensource.html
>>>=20
>>> Kitware offers ITK Training Courses, for more information visit:
>>> http://kitware.com/products/protraining.html
>>>=20
>>> Please keep messages on-topic and check the ITK FAQ at:
>>> http://www.itk.org/Wiki/ITK_FAQ
>>>=20
>>> Follow this link to subscribe/unsubscribe:
>>> http://www.itk.org/mailman/listinfo/insight-developers
>>=20
>> _______________________________________________
>> Powered by www.kitware.com
>>=20
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>=20
>> Kitware offers ITK Training Courses, for more information visit:
>> http://kitware.com/products/protraining.html
>>=20
>> Please keep messages on-topic and check the ITK FAQ at:
>> http://www.itk.org/Wiki/ITK_FAQ
>>=20
>> Follow this link to subscribe/unsubscribe:
>> http://www.itk.org/mailman/listinfo/insight-developers
>>=20