From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by sourceware.org (Postfix, from userid 48) id 2F3E63857737; Mon, 11 Sep 2023 15:28:11 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2F3E63857737 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org; s=default; t=1694446091; bh=99l7Rr/Yo9J/Sh7lQLYvJOyRn55b4jChsHO1bGrR/Ig=; h=From:To:Subject:Date:In-Reply-To:References:From; b=aJIsPx6U2sbQKrRHOiAWPR2pa1licrAerxBEyp8mDoxISZQrNrj0V2PxaP3jRJJYY RS48AK/+dWXFeM+idp6l81y0l034V2SONSkorE5OUJ+4s4oHIKnsEVV5n17+IkpZ8J c4cB75HAbgjmSlMHIgvrnMz/EgvOxXe2CJoWfkfw= From: "john.soo+gcc-bugzilla at arista 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 15:28:07 +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: john.soo+gcc-bugzilla at arista 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 #12 from John Soo --- I think the general problem in that issue is that ARG_MAX is not respected = when the driver (or any subprocess) execs things on linux. I think that it is not the same as the original issue here, though. > I don't know if its going to be helpful to see that patch as a guide Do you think using response files like in pex-win32.c in pex-unix.c could h= elp? I tried this out and it seems like this may not solve all the ARG_MAX probl= ems.=