From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from resdmta-c1p-023852.sys.comcast.net (resdmta-c1p-023852.sys.comcast.net [IPv6:2001:558:fd00:56::c]) by sourceware.org (Postfix) with ESMTPS id 78C093858D20 for ; Tue, 8 Aug 2023 13:33:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 78C093858D20 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=comcast.net Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=comcast.net Received: from resomta-c1p-022590.sys.comcast.net ([96.102.18.239]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resdmta-c1p-023852.sys.comcast.net with ESMTP id TL9BqIa6uqAgLTMq9qtxPM; Tue, 08 Aug 2023 13:33:37 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1691501617; bh=M6uTYvU4iF5lb/Wm5MzPWDJolpLsaJ8ZCqIGZf0v4iA=; h=Received:Received:Content-Type:Mime-Version:Subject:From:Date: Message-Id:To:Xfinity-Spam-Result; b=IuF8UjvCur7bQiXNrkKRG7JbRoueuOyyjsM3Q4NSlVf2gd/w/Bcqra6ppZvh9A8gr CKT9md0b3U93ud0Q2MFbhpMlva2uNHO/m9TdujZYISJfw+VIRe4pE3N72Re6hgWDo6 brMm1MDE5qHE9OzSXjyPpSLRyEzL86TX+GbhJ31pZJV5cxyVSODW8Pmq6aLu4p7dzw BMjV1KrpaXWYruygzffgTl2jKdiaERSP4oYoezq6/ESsvAX13ur2VhfD/WKNZs5BYd tATdwGOdJU7/oyPnIQ7flyAXUnzuz8wM9JF0ujYL5fJGx6y1PRwZkfKdPXq0AdI1LY u7RTf4qMaUg5Q== Received: from smtpclient.apple ([73.60.223.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 256/256 bits) (Client did not present a certificate) by resomta-c1p-022590.sys.comcast.net with ESMTPSA id TMq6qFZxGIGgTTMq7q2nJ1; Tue, 08 Aug 2023 13:33:36 +0000 X-Xfinity-VAAS: gggruggvucftvghtrhhoucdtuddrgedviedrledvgdeihecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucevohhmtggrshhtqdftvghsihdpqfgfvfdppffquffrtefokffrnecuuegrihhlohhuthemuceftddunecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpegtggfuhfgjffevgffkfhfvofesthhqmhdthhdtvdenucfhrhhomheprfgruhhlucfmohhnihhnghcuoehprghulhhkohhnihhnghestghomhgtrghsthdrnhgvtheqnecuggftrfgrthhtvghrnhepveekveelffeliefgiedufeehgeejtdfhgedujeehueekiedtgfetffevgffggfdvnecukfhppeejfedriedtrddvvdefrddutddunecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehhvghlohepshhmthhptghlihgvnhhtrdgrphhplhgvpdhinhgvthepjeefrdeitddrvddvfedruddtuddpmhgrihhlfhhrohhmpehprghulhhkohhnihhnghestghomhgtrghsthdrnhgvthdpnhgspghrtghpthhtohepiedprhgtphhtthhopehjrghkuhgssehrvgguhhgrthdrtghomhdprhgtphhtthhopehrihgthhgrrhgurdhguhgvnhhthhgvrhesghhmrghilhdrtghomhdprhgtphhtthhopehsihguughhvghshhesghhothhplhhtrdhorhhgpdhrtghpthhtohepughjvgdrghgttgesghhmrghilhdrtghomhdprhgtphhtthhopehgtggtqdhprghttghhvghssehgtggtrdhgnhhurdhorhhgpdhrtghpthhtoheptggrrhhlohhssehrvgguhhgrthdrtghomh X-Xfinity-VMeta: sc=-100.00;st=legit Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 16.0 \(3696.120.41.1.4\)) Subject: Re: [RFC] GCC Security policy From: Paul Koning In-Reply-To: Date: Tue, 8 Aug 2023 09:33:34 -0400 Cc: Richard Biener , Siddhesh Poyarekar , David Edelsohn , GCC Patches , Carlos O'Donell Content-Transfer-Encoding: quoted-printable Message-Id: <9390F610-3E72-4D54-9DE2-432BC7C65A1E@comcast.net> References: <5dab0019-a28e-f6b1-c822-9217d4d2f59f@gotplt.org> To: Jakub Jelinek X-Mailer: Apple Mail (2.3696.120.41.1.4) X-Spam-Status: No, score=-2.8 required=5.0 tests=BAYES_00,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_FROM,SPF_HELO_PASS,SPF_PASS,TXREP autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: > On Aug 8, 2023, at 9:01 AM, Jakub Jelinek via Gcc-patches = wrote: >=20 > On Tue, Aug 08, 2023 at 02:52:57PM +0200, Richard Biener via = Gcc-patches wrote: >> There's probably external tools to do this, not sure if we should = replicate >> things in the driver for this. >>=20 >> But sure, I think the driver is the proper point to address any of = such >> issues - iff we want to address them at all. Maybe a nice little >> google summer-of-code project ;) >=20 > What I'd really like to avoid is having all compiler bugs (primarily = ICEs) > considered to be security bugs (e.g. DoS category), it would be = terrible to > release every week a new compiler because of the "security" issues. Indeed. But my answer would be that such things are not DoS issues. = DoS means that an external input, over which you have little control, is = impairing service. In the case of a compiler, if feeding it bad source = code X.c causes it to crash, the answer is "well, then don't do that". paul