From owner-freebsd-current@FreeBSD.ORG  Sun Feb 17 13:16:05 2013
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115])
 by hub.freebsd.org (Postfix) with ESMTP id D6847433;
 Sun, 17 Feb 2013 13:16:05 +0000 (UTC)
 (envelope-from kpaasial@gmail.com)
Received: from mail-we0-x234.google.com (mail-we0-x234.google.com
 [IPv6:2a00:1450:400c:c03::234])
 by mx1.freebsd.org (Postfix) with ESMTP id 2A57681A;
 Sun, 17 Feb 2013 13:16:04 +0000 (UTC)
Received: by mail-we0-f180.google.com with SMTP id k14so3934880wer.25
 for <multiple recipients>; Sun, 17 Feb 2013 05:16:04 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:x-received:in-reply-to:references:date:message-id
 :subject:from:to:cc:content-type;
 bh=s4QB0piSvN+2v1/uPjxZ4A4iUt+0vkayd1YG7SlQuEg=;
 b=XDZEqdELQkbAGHtZrnYIZhdRyq80+23BgLAMYdaOBI0pqjlCuhE5NkmpRqhIEPJK5I
 22+yKY4kTFJU0Lh/LNBJB/2ivLEe0ts0HI+UNq9ngfrTlULC7eOrQYAYj8hfyUScHfkE
 W9Y1x2eCkbmlpj0GsCUBvFrBIZAVd7QF/+wgJXyjaWhU8825HuWhkmMn5hLwA65ZpN8b
 PkvqEtogV9r77s9pZF/LUDLgVuhI4Yp2djiSkdd0gmhZlKZogN/otyXm2d4dGSMZO1KI
 QEJhhTByU9inIsVav5wUsfcHylXqFnMwZyh8VRIDW9uEiKcyjBMu+GTJE+XH0DPb0Iir
 CO2A==
MIME-Version: 1.0
X-Received: by 10.194.122.199 with SMTP id lu7mr13499261wjb.42.1361106964377; 
 Sun, 17 Feb 2013 05:16:04 -0800 (PST)
Received: by 10.216.120.193 with HTTP; Sun, 17 Feb 2013 05:16:04 -0800 (PST)
In-Reply-To: <20130213022215.GK99263@hades.panopticon>
References: <CA+7WWSeFh9sJyo3kKD5wTEHoyTSjR6TuDDgDCV5Nhc_wMzVUkg@mail.gmail.com>
 <20130213022215.GK99263@hades.panopticon>
Date: Sun, 17 Feb 2013 15:16:04 +0200
Message-ID: <CA+7WWSenB6bwvtVfyFvgE-ebz3LgcMMrhHqUkOvL1wA8vRpvtA@mail.gmail.com>
Subject: Re: CLANG and -fstack-protector
From: Kimmo Paasiala <kpaasial@gmail.com>
To: Dmitry Marakasov <amdmi3@amdmi3.ru>
Content-Type: text/plain; charset=UTF-8
Cc: FreeBSD current <freebsd-current@freebsd.org>, freebsd-stable@freebsd.org
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.14
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Feb 2013 13:16:05 -0000

On Wed, Feb 13, 2013 at 4:22 AM, Dmitry Marakasov <amdmi3@amdmi3.ru> wrote:
> * Kimmo Paasiala (kpaasial@gmail.com) wrote:
>
>> Does the -fstack-protector option work on CLANG 3.1 and 3.2?
>>
>> There is thread on FreeBSD forums about the stack protector and ports
>> and I'm wondering if it's possible to use the -fstack-protector option
>> with CLANG.
>>
>> http://forums.freebsd.org/showthread.php?t=36927
>
> You might be interested in this patch:
>
> https://github.com/AMDmi3/freebsd-ports-mk/compare/master...stack-protector
>
> afaik, in prior discussion some years ago an issue was mentioned that
> some ports don't build with stack-protector, so I suggested to introduce
> STACK_PROTECTOR_SAFE/_UNSAFE knobs similar to what we have for
> MAKE_JOBS_SAFE_/_UNSAFE (we might actually only need
> STACK_PROTECTOR_UNSAFE, as unlike MAKE_JOBS, build errors caused by
> enabling stack protector are not transient, so we can have an exp-run
> to just mark all uncompatible ports and consider all others compatible).
>
> If there's interest in this, I can refresh the patch and submit it.
>

Yes, this is very much what I had in mind. Please submit it :)

-Kimmo