Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Ralf Baechle <ralf@linux-mips.org>
To: Glauber de Oliveira Costa <glommer@gmail.com>
Cc: Chris Wedgwood <cw@f00f.org>, Adrian Bunk <bunk@kernel.org>,
	Randy Dunlap <randy.dunlap@oracle.com>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jarek Poplawski <jarkao2@o2.pl>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	linux-mips@linux-mips.org
Subject: Re: RFC: drop support for gcc < 4.0
Date: Wed, 22 Aug 2007 19:15:32 +0100	[thread overview]
Message-ID: <20070822181532.GB3362@linux-mips.org> (raw)
In-Reply-To: <5d6222a80708211341s63f8c1eau922f018e66db49f4@mail.gmail.com>

On Tue, Aug 21, 2007 at 05:41:04PM -0300, Glauber de Oliveira Costa wrote:

> Last time I tried a mips build, it would fail the compile unless I was
> using _exactly_ 3.4.4 (I didn't tried older versions, but did try
> 3.4.6, for ex.). So I also think the 3.4 series will still have to be
> around for a while.

I don't know what broken MIPS platform you've tried.  I keep changing
between compiler versions all the time just so I can ensure builds with
older compilers keep working until we officially deciede to drop support
for them.  So the minimum compiler version for 32-bit MIPS kernels is
gcc 3.2 and for 64-bit kernel gcc 3.3.

But for sake of sanity and productivity I definately don't mind dumping
support for gcc < 4.0 or maybe even 4.1.  And while we're at it, let's
deprecate ancient binutils version as well.  A minimum version of 2.17
would be nice as I could get rid of lads of .word sillyness which is
needed to support older binutils.

  Ralf

  parent reply	other threads:[~2007-08-22 18:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070821132038.GA22254@ff.dom.local>
     [not found] ` <20070821093103.3c097d4a.randy.dunlap@oracle.com>
     [not found]   ` <20070821173550.GC30705@stusta.de>
     [not found]     ` <20070821182505.GA20968@puku.stupidest.org>
2007-08-21 20:41       ` RFC: drop support for gcc < 4.0 Glauber de Oliveira Costa
2007-08-21 20:56         ` Segher Boessenkool
2007-08-21 21:01           ` Glauber de Oliveira Costa
2007-08-22  6:59         ` Thomas Bogendoerfer
2007-08-22 18:15         ` Ralf Baechle [this message]
     [not found]     ` <20070821191959.GC2642@bingen.suse.de>
     [not found]       ` <20070821195433.GE30705@stusta.de>
     [not found]         ` <alpine.LFD.0.999.0708211306560.30176@woody.linux-foundation.org>
     [not found]           ` <20070821202113.GF30705@stusta.de>
     [not found]             ` <27c412eea99f1f80a3002e9668bd31f8@kernel.crashing.org>
     [not found]               ` <20070821212129.GG30705@stusta.de>
     [not found]                 ` <17c0b56b663fce6f28b46e3c42dfbaf9@kernel.crashing.org>
2007-08-22  6:07                   ` Jarek Poplawski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070822181532.GB3362@linux-mips.org \
    --to=ralf@linux-mips.org \
    --cc=akpm@linux-foundation.org \
    --cc=bunk@kernel.org \
    --cc=cw@f00f.org \
    --cc=glommer@gmail.com \
    --cc=jarkao2@o2.pl \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@linux-mips.org \
    --cc=randy.dunlap@oracle.com \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox