On 06/20/2011 03:22 PM, Anton Shterenlikht wrote:
On Mon, Jun 20, 2011 at 12:44:06PM +0200, Tobias Burnus wrote:
compiler. [Personal observation: On x86-64, gfortran is everywhere
installed, the Intel compiler is very often, on two systems I also saw
PGI - but I have never seen PathScale.]
w
On Mon, Jun 20, 2011 at 12:44:06PM +0200, Tobias Burnus wrote:
>
> compiler. [Personal observation: On x86-64, gfortran is everywhere
> installed, the Intel compiler is very often, on two systems I also saw
> PGI - but I have never seen PathScale.]
we use it:
https://www.acrc.bris.ac.uk/acrc/p
On Sun, Jun 19, 2011 at 11:04:09PM +0700, "C. Bergstr?m" wrote:
> 3) Fortran HPC community as a whole - The majority of Fortran users I
> know work in or around HPC. (I may be biased) With that I can't say
> most of them care about open source at all. (Some do) They buy/use
> PathScale/PGI/I
On 06/19/2011 06:04 PM, "C. Bergström" wrote:
3) Fortran HPC community as a whole - The majority of Fortran users I
know work in or around HPC. (I may be biased) With that I can't say
most of them care about open source at all. (Some do) They buy/use
PathScale/PGI/Intel and for the larger l
On Sun, 19 Jun 2011 21:32:25 +0200, "Mikael Morin" wrote:
> I personally see no problem gfortran being reused in pathscale's compiler as
> long as pathscale's contribution is libre (free). It can even improve code
> quality to make gfortran backend independant (probably not much as the IR
> generat
"C. Bergström" writes:
> 1) What's wrong with commercial software?
I don't want to get into licensing fight, and I don't know anything
about the history of the Fortran frontend, but I do want to suggest a
correction to your wording. I'm not aware of any GCC contributor who
thinks there is anyth
On Sunday 19 June 2011 20:30:17 Christopher Bergström wrote:
> Nothing cloudy
>
> 1) Vet the codebase (stated this clearly)
> 2) Listen to what people say - (What needs to be worked on, are people
> open to things like dual licensing, what's the future of Fortran,
> etc..)
>
> For whatever reason
On Mon, Jun 20, 2011 at 12:02 AM, Janus Weil wrote:
> 2011/6/19 "C. Bergström" :
>> In this case I serve the end user/community and not directly open source.
>> Why? Would it be good for Fortran if a F2K3 front-end was freely available
>> under a commercially friendly license? (This is a deeper
Hi all,
I'm sorry if I made this turn into a discussion of the benefits of Free
Software, just two short points ...
On 2011-06-19 18:58, Steve Kargl wrote:
On Sun, Jun 19, 2011 at 11:04:09PM +0700, "C. Bergstr?m" wrote:
Andy started the project and at the time of the fork still was the
majo
2011/6/19 "C. Bergström" :
> In this case I serve the end user/community and not directly open source.
> Why? Would it be good for Fortran if a F2K3 front-end was freely available
> under a commercially friendly license? (This is a deeper question I'd love
> feedback on)
From my point of view a
On Sun, Jun 19, 2011 at 11:04:09PM +0700, "C. Bergstr?m" wrote:
>
>
> I can't say I really care about Andy's alleged copyright infringement.
> (My general point on matters like this is litigate or shut up. We're
> all here to get work done and licensing (licensing trolls and I don't
> mean y
On 06/19/11 10:03 PM, Tobias Schlüter wrote:
Hi Christopher,
On 2011-06-18 14:39, "C. Bergström" wrote:
On 06/18/11 05:16 PM, Toon Moene wrote:
On 06/18/2011 12:12 PM, Toon Moene wrote:
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
Hi
We're in the process of considering contribut
Hi Christopher,
On 2011-06-18 14:39, "C. Bergström" wrote:
On 06/18/11 05:16 PM, Toon Moene wrote:
On 06/18/2011 12:12 PM, Toon Moene wrote:
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
Hi
We're in the process of considering contributing to gfortran for a
special project, but when
On Sun, Jun 19, 2011 at 12:13:25AM +0700, "C. Bergstr?m" wrote:
> On 06/18/11 11:41 PM, Steve Kargl wrote:
> >Good luck with that endeavor. After the gfortran fork,
> >a certain individual would routinely obfusicate the code
> >in one of the repositories via gratuitious code motion,
> >varaible r
On 06/18/11 11:41 PM, Steve Kargl wrote:
Good luck with that endeavor. After the gfortran fork,
a certain individual would routinely obfusicate the code
in one of the repositories via gratuitious code motion,
varaible renaming, and whitespace munging. This was an
attempt to neutered diff. Thi
On Sat, Jun 18, 2011 at 06:22:21PM +0700, Christopher Bergstr?m wrote:
> 2011/6/18 Toon Moene :
> > On 06/18/2011 01:02 PM, "C. Bergstr?m" wrote:
> >> On 06/18/11 05:16 PM, Toon Moene wrote:
> >>> On 06/18/2011 12:12 PM, Toon Moene wrote:
> On 06/18/2011 05:05 AM, Christopher Bergstr?m wrote:
On 06/18/11 05:16 PM, Toon Moene wrote:
On 06/18/2011 12:12 PM, Toon Moene wrote:
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
Hi
We're in the process of considering contributing to gfortran for a
special project, but when we started to vet the codebase we hit a bump
in lack of comm
2011/6/18 Toon Moene :
> On 06/18/2011 01:02 PM, "C. Bergström" wrote:
>
>> On 06/18/11 05:16 PM, Toon Moene wrote:
>
>>> On 06/18/2011 12:12 PM, Toon Moene wrote:
>
>>>
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
> Hi
>
> We're in the process of considering contribut
On 06/18/2011 01:02 PM, "C. Bergström" wrote:
On 06/18/11 05:16 PM, Toon Moene wrote:
On 06/18/2011 12:12 PM, Toon Moene wrote:
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
Hi
We're in the process of considering contributing to gfortran for a
special project, but when we start
On 06/18/11 05:16 PM, Toon Moene wrote:
On 06/18/2011 12:12 PM, Toon Moene wrote:
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
Hi
We're in the process of considering contributing to gfortran for a
special project, but when we started to vet the codebase we hit a bump
in lack of comm
On 06/18/2011 12:12 PM, Toon Moene wrote:
On 06/18/2011 05:05 AM, Christopher Bergström wrote:
Hi
We're in the process of considering contributing to gfortran for a
special project, but when we started to vet the codebase we hit a bump
in lack of commit history.
Additional information is he
21 matches
Mail list logo