From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id B3E4D3858C5E; Mon, 11 Sep 2023 08:34:12 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B3E4D3858C5E DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1694421252; bh=adYE8y3/LhJyiGEaMPnHO5UsYxIQKhNKl1rJQrdJYho=; h=From:To:Subject:Date:In-Reply-To:References:From; b=q+bEAALTDeelYjBEoRFbCmfeiWNKwHnwGJLCto0wWeaCNUMclEXrsVktzr19/To5N uqGEpolabRLVWgrEriiqDdSB56YsK66cOIFGO4O0BcmQpBjyiP720nX9hXj+Xj1O8p VN5o31s420FetkCt6iT9GMSHj1qeimUVMrPqzTL4= From: "costas.argyris at gmail dot com" To: gcc-bugs@gcc.gnu.org Subject: [Bug driver/86030] specs file processing does not create response files for input directories Date: Mon, 11 Sep 2023 08:34:10 +0000 X-Bugzilla-Reason: CC X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: gcc X-Bugzilla-Component: driver X-Bugzilla-Version: unknown X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: costas.argyris at gmail dot com X-Bugzilla-Status: NEW 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=3D86030 --- Comment #11 from Costas Argyris --- (In reply to John Soo from comment #10) > I'm also not sure > https://gcc.gnu.org/git/?p=3Dgcc.git;a=3Dcommitdiff; > h=3D180ebb8a24d24fc5b105f2257d6216f6dfde62df fixes the collect bug because > collect uses collect_execute instead of the pex_* exec functions. That patch was only meant to deal with the 32K command line length limitati= on on Windows hosts, for programs spawned with the pex functions (to my knowle= dge, this is how the driver spawns its sub-programs like the compiler, assembler= and linker). In this PR though the problem appears to be something else which I am not familiar with, so I don't know if its going to be helpful to see that patch= as a guide. I only put the reference in the hopes that it solved this as well because it looked similar, but it doesn't look like it. You may need to = come up with a completely new solution for all I know.=