From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id D401C3858D33; Fri, 6 Jan 2023 14:39:25 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org D401C3858D33 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1673015965; bh=rM8mE8S6oXtgd0Mk/oPmyFLy1za1Dh6rrcvUyRlq7fI=; h=From:To:Subject:Date:In-Reply-To:References:From; b=oJWMCnuv8DuoXiRnwS76Blow7bO6FtZ8hkKChHObz8ayEaq+fb11AyWV1X9aapt20 Sz+I9SpJs2uScSC5ffiLVtQ6GyH+OB8w3yxnXcHAxiwJaFQG+XHJjJQjbDAWrinl9q g+usw252ZDLb8XEoFywCFLOdjbfCUN6GCcvXdVxg= From: "iains at gcc dot gnu.org" To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108182] gm2 driver mishandles target and multilib options Date: Fri, 06 Jan 2023 14:39:25 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: modula2 X-Bugzilla-Version: 13.0 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: iains at gcc dot gnu.org X-Bugzilla-Status: NEW X-Bugzilla-Resolution: X-Bugzilla-Priority: P3 X-Bugzilla-Assigned-To: gaius 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=3D108182 --- Comment #6 from Iain Sandoe --- (In reply to Iain Sandoe from comment #5) > (In reply to Gaius Mulley from comment #4) > > Created attachment 54184 [details] > > Potential fix for target multilib_dir handling -m and -f. > >=20 > > Work in progress. >=20 > 1. (I think) the string you need is "multilib_os_dir" not "multilib_dir" > (but ICBW about that .. there are many twisty passages in the determinati= on > of these things). It seems that I was wrong about this ... at least on x86_65-linux-gnu (which does use MULTILIB_OSDIRNAMES) and *-darwin* (which does not). It seems to DTRT. (tested on linux with a 32b multilib) > 2. The concern remains that the language spec handler is run pretty much > first in the stack and there are several other claims on the command line > that could have specs that alter (or add) flags to the command line, givi= ng > a different outcome to the computation of mulilib_{,os_}dir. >=20 > perhaps it would be a good idea to post this and ask the opinion of someo= ne > like Joseph on the direction. So ... the proposed patch seems to fix the problem for Darwin and X86_64 Li= nux. definitely post it! (we still need to fix the issue with the shared libraries hidden by the additional -Ls but that's a one-line patch)=