From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
	id BFFE53858C00; Fri, 15 Sep 2023 19:22:13 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org BFFE53858C00
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
	s=default; t=1694805733;
	bh=08JgtN8GCsqjh0Zt6icSWrOxLsfJ5qnKcqUqKCjhPf8=;
	h=From:To:Subject:Date:In-Reply-To:References:From;
	b=B8xPbUwyUp2vvZZYRS46bWmucTi0FIL8aH0H5TZYWp1ulu4dNNtO5+0ZcnxEHPmTZ
	 157xGIZpvQxl9I4NRXTVW+tFD2D01+dpensKB5ml48N/uEIU69OtZJO6hUHkobfxhh
	 0Nojs3qjARj6a6ez6VWQxk6LzcjtzEaatTYlnd1w=
From: "john.soo+gcc-bugzilla at arista dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug driver/86030] specs file processing does not create response
 files for input directories
Date: Fri, 15 Sep 2023 19:22:12 +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: <bug-86030-4-KA33lGqMXL@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-86030-4@http.gcc.gnu.org/bugzilla/>
References: <bug-86030-4@http.gcc.gnu.org/bugzilla/>
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: <gcc-bugs.sourceware.org>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D86030

--- Comment #16 from John Soo <john.soo+gcc-bugzilla at arista dot com> ---
It is actually somewhat likely that ARG_MAX will be hit when running on lin=
ux
because it is hit when the stack can't contain enough pointers to contain a=
rgv
and environ (see exec.c in the kernel
https://github.com/torvalds/linux/blob/master/fs/exec.c#L509).

The bad news is that response files can only mitigate the problem since env=
iron
must also be small enough to fit into an execv* call.

Is there a reasonable way to keep only the env vars required to exec
subprocesses?=