public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "iains at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug modula2/108182] gm2 driver mishandles target and multilib options Date: Mon, 02 Jan 2023 12:38:03 +0000 [thread overview] Message-ID: <bug-108182-4-QeR8yJT1YJ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-108182-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=108182 --- Comment #2 from Iain Sandoe <iains at gcc dot gnu.org> --- computing the multilib_os_dir in the language driver is not going to be easy/reliably correct, since that code is called very early and the specs applied later could well modify the command line options. On IRC I had suggested that to mitigate thus it might be possible to defer the computation by using the "%M" spec to insert the relevant multilib_os_dir entries. However, that would mean moving the production of the -I command line entries to a language spec. At the moment I cannot see how to implement that - since there are no specs to substitute for $libdir etc. So, at present, ISTM that the most reliable approach would be to follow what the c-fmaily does and compute the language-specific include paths early in the front end. ---- As noted in PR108259, the '-L' entries are not, in fact, needed (actually they break the discovery of the shared libraries) so that this part of the process can be simplified (and there is no need to consider the pre-link callback we were discussing). It seems increasingly likely that simplifying the library to a single runtime with the process of deciding which APIs are available decided by the FE is probably going to resolve a bunch of difficulties and simplify the driver at the same time (0.02GBP, only, no patches at this time).
next prev parent reply other threads:[~2023-01-02 12:38 UTC|newest] Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-19 23:36 [Bug modula2/108182] New: " iains at gcc dot gnu.org 2022-12-19 23:36 ` [Bug modula2/108182] " iains at gcc dot gnu.org 2022-12-19 23:45 ` pinskia at gcc dot gnu.org 2023-01-02 12:38 ` iains at gcc dot gnu.org [this message] 2023-01-03 21:20 ` gaius at gcc dot gnu.org 2023-01-04 1:55 ` gaius at gcc dot gnu.org 2023-01-05 17:09 ` iains at gcc dot gnu.org 2023-01-06 14:39 ` iains at gcc dot gnu.org 2023-01-06 21:16 ` gaius at gcc dot gnu.org 2023-01-06 21:23 ` gaius at gcc dot gnu.org 2023-01-09 1:28 ` gaius at gcc dot gnu.org 2023-01-09 15:08 ` gaius at gcc dot gnu.org 2023-01-09 20:35 ` iains at gcc dot gnu.org 2023-01-10 11:39 ` iains at gcc dot gnu.org 2023-01-11 16:16 ` iains at gcc dot gnu.org 2023-01-12 23:49 ` iains at gcc dot gnu.org 2023-01-13 0:15 ` iains at gcc dot gnu.org 2023-01-17 16:59 ` iains at gcc dot gnu.org 2023-01-23 17:29 ` cvs-commit at gcc dot gnu.org 2023-01-23 17:34 ` iains at gcc dot gnu.org 2023-01-25 15:24 ` cvs-commit at gcc dot gnu.org 2023-01-25 15:46 ` iains at gcc dot gnu.org 2023-01-27 8:48 ` cvs-commit at gcc dot gnu.org
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=bug-108182-4-QeR8yJT1YJ@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).