public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "slyfox at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/111527] COLLECT_GCC_OPTIONS option hits single-variable limits too early Date: Fri, 22 Sep 2023 08:15:13 +0000 [thread overview] Message-ID: <bug-111527-4-3MmvS0ymSV@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-111527-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111527 --- Comment #2 from Sergei Trofimovich <slyfox at gcc dot gnu.org> --- (In reply to Richard Biener from comment #1) > Hm, but the COLLECT_GCC_OPTIONS variable is only used for communicating > between the driver and the linker, the options therein are individually > passed to the program execved? AFAIU the driver sets `COLLECT_GCC_OPTIONS` variable and never unsets it. As a result it affects all the `exevce() calls. Be it `cc1`, `as` or anything else regardless of the fact if it uses the variable or not. `cc1` is probably the first casualty. As a simplistic example here we break `ls` with too large environment file: $ COLLECT_GCC_OPTIONS=$(printf "%0*d" 200000 0) ls -bash: /run/current-system/sw/bin/ls: Argument list too long > You are maybe looking for the -f*-map options to take a file as input > containing multiple mappings? `NixOS` is also occasionally hottong the same limit by passing too many include an library paths: -I/nix/store/hash1-foo/include -I/nix/store/hash2-bar/include ... -L/nix/store/hash1-foo/lib -L/nix/store/hash2-bar/lib ... -Wl,-rpath,/nix/store/hash1-foo/lib -Wl,-rpath,/nix/store/hash2-bar/lib I wonder if we could solve all of these limitations here by at least avoiding `COLLECT_GCC_OPTIONS`. But otherwise if generic fix is too invasive change then passing a mapping file should do as well. What would be an acceptable for of the file? A new option, like? -fmacro-prefix-map-file=./foo with entries of exactly the same form $ cat foo /nix/store/hash1-foo=/nix/store/00000000-foo /nix/store/hash2-bar=/nix/store/00000000-bar ... Or maybe reuse existing -fmacro-prefix-map= and use response-style file input? Like -fmacro-prefix-map=@./foo. clang would probably need the same handling if we were to extend the driver.
next prev parent reply other threads:[~2023-09-22 8:15 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-09-21 19:06 [Bug driver/111527] New: " slyfox at gcc dot gnu.org 2023-09-22 5:22 ` [Bug driver/111527] " rguenth at gcc dot gnu.org 2023-09-22 8:15 ` slyfox at gcc dot gnu.org [this message] 2024-03-16 9:52 ` deepadeepthi98 at gmail dot com 2024-03-16 9:53 ` deepadeepthi98 at gmail dot com 2024-03-16 20:18 ` slyfox at gcc dot gnu.org 2024-05-06 11:39 ` deepadeepthi98 at gmail dot com 2024-05-06 11:42 ` deepadeepthi98 at gmail dot com 2024-05-06 16:02 ` pinskia at gcc dot gnu.org 2024-05-15 10:58 ` deepadeepthi98 at gmail dot com 2024-05-15 11:00 ` deepadeepthi98 at gmail dot com 2024-05-18 21:33 ` pinskia 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-111527-4-3MmvS0ymSV@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).