From owner-freebsd-mips@FreeBSD.ORG Thu Jul 8 09:15:21 2010 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 96252106564A; Thu, 8 Jul 2010 09:15:21 +0000 (UTC) (envelope-from c.jayachandran@gmail.com) Received: from mail-vw0-f54.google.com (mail-vw0-f54.google.com [209.85.212.54]) by mx1.freebsd.org (Postfix) with ESMTP id 2FD128FC1B; Thu, 8 Jul 2010 09:15:20 +0000 (UTC) Received: by vws6 with SMTP id 6so1047056vws.13 for ; Thu, 08 Jul 2010 02:15:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=rxML4OZtSvGaLUfvL1TpnGmPUcf77omnpqLFYprBick=; b=gpznNzCapbkw21Tit6dsn5Y032e3dfyj9rHUWsplG/zUUul/mXlbnVqrls1eKEp7F6 d9KEIQPmlk98gw/3yFU1lCc0LobmlbXnTVo1fkxHtdiuS0SyTqlRn/9u13H8ATQmd1DS 47kVYmSs64MavlOEqWkQbukpln17ULo9IVMFs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=uijs3JTuUOYHF4QRyVPrXXIrIhcp1sc1mzxen4oYzZtE75ZUaIUn8SkGpqE2kAuLKK tXleRac1x1T/J971+TAEtRTE7UnWBtG3YFSxkMYSZiqjkPExCC95hn67ruFRuqgNJ5VG kZayJX05wtOGcKFLU5wskCZUNMhdye5Jj7nGs= MIME-Version: 1.0 Received: by 10.220.158.9 with SMTP id d9mr4140760vcx.250.1278580516574; Thu, 08 Jul 2010 02:15:16 -0700 (PDT) Received: by 10.220.194.4 with HTTP; Thu, 8 Jul 2010 02:15:16 -0700 (PDT) In-Reply-To: References: <20100708.021250.1099368555950605809.imp@bsdimp.com> Date: Thu, 8 Jul 2010 14:45:16 +0530 Message-ID: From: "Jayachandran C." To: Juli Mallett Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-mips@freebsd.org Subject: Re: Merging 64 bit changes to -HEAD - part 4 X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jul 2010 09:15:21 -0000 On Thu, Jul 8, 2010 at 1:59 PM, Juli Mallett wrote: > On Thu, Jul 8, 2010 at 01:12, M. Warner Losh wrote: >> In message: >> =A0 =A0 =A0 =A0 =A0 =A0"Jayachandran C." writ= es: >> : ldscript-64.patch >> : =A064 bit linker script (JC) >> : =A0linker script for 64 bit compilation, and XLR configuration file. >> >> I wonder if the octeon ld script can be merged or if we can use this >> for octeon. =A0Some investigation is warranted, I think... > > No investigation needed. > > U-Boot, at least on Octeon, requires only one (executable) program > header, so it's necessary for Octeon to use its own ldscript -- I > suspect other bootloaders have likewise weird constraints. =A0That said, > there's really no need for all of these separate linker scripts, > assuming you use buildkernel and have TARGET_ABI set right when you > build kernel-toolchain. =A0I use a single linker script for all Octeon > kernels, I think. =A0You don't need to specify the output format. We could probably make the single script you have as the standard script if it works for most bootloaders. I still don't like the way ARCH_FLAGS and LDSCRIPT_NAME needs to be specified in the conf file - this could be taken from TARGET_ABI too... JC.