On Fri, Jul 2, 2010 at 9:55 AM, Segher Boessenkool
wrote:
> [I proposed removing RIOS support, since it heavily gets in the way
> for my project exposing the XER[CA] flag].
>
>> My argument is simply this, sorry if it wasn't clear in the last
>> email, bottom line up front:
>> - It can just as eas
[I proposed removing RIOS support, since it heavily gets in the way
for my project exposing the XER[CA] flag].
My argument is simply this, sorry if it wasn't clear in the last
email, bottom line up front:
- It can just as easily be removed in the future if it is broken for
more than one release
On Tue, Jun 29, 2010 at 6:51 PM, David Edelsohn wrote:
> On Tue, Jun 29, 2010 at 6:18 PM, Kevin Bowling
> wrote:
>
>> This is an unfortunate attitude many people have in free software
>> these days, especially big business contributors with profit-aligned
>> motives. Linus weighs in on a simila
On Tue, Jun 29, 2010 at 7:07 PM, Kevin Bowling wrote:
> My argument is simply this, sorry if it wasn't clear in the last
> email, bottom line up front:
> - It can just as easily be removed in the future if it is broken for
> more than one release rather than evicting support.
> - It shouldn't add
On Tue, Jun 29, 2010 at 6:18 PM, Kevin Bowling wrote:
> This is an unfortunate attitude many people have in free software
> these days, especially big business contributors with profit-aligned
> motives. Linus weighs in on a similar dissent here:
> http://lwn.net/Articles/339455/.
This is just
On Tue, Jun 29, 2010 at 4:07 PM, Kevin Bowling wrote:
> My argument is simply this, sorry if it wasn't clear in the last
> email, bottom line up front:
> - It can just as easily be removed in the future if it is broken for
> more than one release rather than evicting support.
> - It shouldn't add
On Tue, Jun 29, 2010 at 3:35 PM, Steven Bosscher wrote:
> On 6/30/10, Kevin Bowling wrote:
>>> GCC's mission is not to
>>> support every system in a computer history museum. Older versions of
>>> GCC created at the time of those systems still will work on those
>>> systems.
>>>
>>
>>
>> This is
On 6/30/10, Kevin Bowling wrote:
>> GCC's mission is not to
>> support every system in a computer history museum. Older versions of
>> GCC created at the time of those systems still will work on those
>> systems.
>>
>
>
> This is an unfortunate attitude many people have in free software
> these d
On Tue, Jun 29, 2010 at 7:09 AM, David Edelsohn wrote:
> On Tue, Jun 29, 2010 at 1:53 AM, Kevin Bowling
> wrote:
>> In the GCC 4.5 announcement:
>>
>> "Support for the classic POWER architecture implemented in the
>> original RIOS and RIOS2 processors of the old IBM RS/6000 product line
>> has b
On Tue, Jun 29, 2010 at 1:53 AM, Kevin Bowling wrote:
> In the GCC 4.5 announcement:
>
> "Support for the classic POWER architecture implemented in the
> original RIOS and RIOS2 processors of the old IBM RS/6000 product line
> has been obsoleted in the rs6000 port. This does not affect the new
> g
On Tue, Jun 29, 2010 at 12:45 AM, Andrew Haley wrote:
> On 06/29/2010 06:53 AM, Kevin Bowling wrote:
>> In the GCC 4.5 announcement:
>>
>> "Support for the classic POWER architecture implemented in the
>> original RIOS and RIOS2 processors of the old IBM RS/6000 product line
>> has been obsoleted
On 06/29/2010 06:53 AM, Kevin Bowling wrote:
> In the GCC 4.5 announcement:
>
> "Support for the classic POWER architecture implemented in the
> original RIOS and RIOS2 processors of the old IBM RS/6000 product line
> has been obsoleted in the rs6000 port. This does not affect the new
> generation
12 matches
Mail list logo
