This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: GCC version bikeshedding

From: Alec Teal <a dot teal at warwick dot ac dot uk>
To: Andi Kleen <andi at firstfloor dot org>
Cc: Paulo Matos <paulo at matos-sorge dot com>, <gcc at gcc dot gnu dot org>
Date: Mon, 21 Jul 2014 15:30:45 +0100
Subject: Re: GCC version bikeshedding
Authentication-results: sourceware.org; auth=none
References: <20140720165506 dot GT3003 at laptop dot redhat dot com> <7564e4f5-8030-4a23-8b0b-b1262265a349 at email dot android dot com> <lqh7at$shq$1 at ger dot gmane dot org> <87tx6b3eka dot fsf at tassilo dot jf dot intel dot com>

On 20/07/14 22:28, Andi Kleen wrote:

Paulo Matos<paulo@matos-sorge.com>  writes:

That's what I understood as well. Someone mentioned to leave the patch
level number to the distros to use which sounded like a good idea.

Sounds like a bad idea, as then there would be non unique gcc versions.
redhat gcc 5.0.2 potentially being completely different from suse gcc
5.0.2

Agreed (no experience, but I wouldn't want to live in a world where whatAndi

describes is the case!)


-Andi

What is "Bikeshedding"? I've not heard this term before and a quicksearch showed

some weird things, and this very thread!

Alec

References:
- GCC version bikeshedding
  - From: Jakub Jelinek
- Re: GCC version bikeshedding
  - From: Richard Biener
- Re: GCC version bikeshedding
  - From: Paulo Matos
- Re: GCC version bikeshedding
  - From: Andi Kleen

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]