From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id E3E0A3894C27; Thu, 20 Jun 2024 22:49:53 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org E3E0A3894C27 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1718923793; bh=76Zy+tYPoX4xOB5M16N9vSEek5KkSVked5oPmlNDngQ=; h=From:To:Subject:Date:In-Reply-To:References:From; b=s9pdXB8BzogGC3b2kXvNaYZ9br8IJmOqJZqWrCoR4WhlAdHD2MrVxW7xu1Moqx0BF CmOZb723xVi2QmOJfsVOgvl8/9zvBVp7mvU3wLTSDZZW2Ax92u3yTUF6KKcSYEpyxU S8zS0IyyhgVeMM7AY62Ag1hF+7q9B0y91PBtiGuI= From: "broly at mac dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug target/115408] regression between gcc 13.3.0 and 14.1.0 using -mips16 and -minterlink-mips16 Date: Thu, 20 Jun 2024 22:49:53 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: target X-Bugzilla-Version: 14.1.0 X-Bugzilla-Keywords: link-failure X-Bugzilla-Severity: normal X-Bugzilla-Who: broly at mac dot com X-Bugzilla-Status: WAITING X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 List-Id: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D115408 --- Comment #13 from gagan sidhu (broly) --- oh i see, i didn't realise that thumb was pure 16 bit. my apologies. so i guess i meant thumb2, which would have the same effect of the mips16/minterlink-mips16 flags that i use to "collapse" 32 bit executables?* https://stackoverflow.com/a/71378041 apparently it's all called thumb though? not trying to escape your (very welcome) correction, but i just wanted to share my surprise at learning thi= s. -- * often a nice savings in binary size. of course i concede if you use a sophisticated compression algorithm on the root file system containing these binaries, there is a significant reductio= n in the benefit of the root filesystem compression (possibly even detrimental).=