From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30671 invoked by alias); 3 Feb 2014 21:12:41 -0000 Mailing-List: contact binutils-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: binutils-owner@sourceware.org Received: (qmail 30660 invoked by uid 89); 3 Feb 2014 21:12:40 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.1 required=5.0 tests=AWL,BAYES_00,RP_MATCHES_RCVD autolearn=ham version=3.3.2 X-HELO: multi.imgtec.com Received: from multi.imgtec.com (HELO multi.imgtec.com) (194.200.65.239) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with (AES256-GCM-SHA384 encrypted) ESMTPS; Mon, 03 Feb 2014 21:12:40 +0000 From: Jack Carter To: Richard Sandiford CC: "H.J. Lu" , "binutils@sourceware.org" Subject: RE: [MIPS] Is it legal for the assembler to generate more than 64K sections? Date: Mon, 03 Feb 2014 21:12:00 -0000 Message-ID: <4CEFBC1BE64A8048869F799EF2D2EEEE4C6F2BA0@BADAG02.ba.imgtec.org> References: <4CEFBC1BE64A8048869F799EF2D2EEEE4C6F2880@BADAG02.ba.imgtec.org> <4CEFBC1BE64A8048869F799EF2D2EEEE4C6F2AA2@BADAG02.ba.imgtec.org> <87mwi87xeu.fsf@talisman.default> <4CEFBC1BE64A8048869F799EF2D2EEEE4C6F2B73@BADAG02.ba.imgtec.org>,<87iosv9alm.fsf@talisman.default> In-Reply-To: <87iosv9alm.fsf@talisman.default> Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-SEF-Processed: 7_3_0_01192__2014_02_03_21_12_37 X-SW-Source: 2014-02/txt/msg00021.txt.bz2 >(.text._ZN4llvm25SmallVectorTemplateCommonIN5clang19RecursiveASTVisitorINS= 1_11AttrVisitorEE10EnqueueJobEvE4backEv[_ZN4llvm25SmallVectorTemplateCommon= IN5clang19RecursiveASTVisitorINS1_11AttrVisitorEE10EnqueueJobEvE4backEv]+0x= 64): >> relocation truncated to fit: R_MIPS_GOT16 against `no symbol' >> >> Basically building LLVM with a MIPS GCC. I noticed that the section >> count was way above 16 bits and seized on that as being the culprit. > >Ah, OK. Looks like a multigot failure at face value. Are you using >recent binutils (2.24)? It has some fixes in that area. I rebased on Thursday. Multigot is a good area for me to look since I am mucking with the got with= ifunc anyway. Cheers, Jack > >Thanks, >Richard