Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 17 Feb 2013 15:16:04 +0200
From:      Kimmo Paasiala <kpaasial@gmail.com>
To:        Dmitry Marakasov <amdmi3@amdmi3.ru>
Cc:        FreeBSD current <freebsd-current@freebsd.org>, freebsd-stable@freebsd.org
Subject:   Re: CLANG and -fstack-protector
Message-ID:  <CA%2B7WWSenB6bwvtVfyFvgE-ebz3LgcMMrhHqUkOvL1wA8vRpvtA@mail.gmail.com>
In-Reply-To: <20130213022215.GK99263@hades.panopticon>
References:  <CA%2B7WWSeFh9sJyo3kKD5wTEHoyTSjR6TuDDgDCV5Nhc_wMzVUkg@mail.gmail.com> <20130213022215.GK99263@hades.panopticon>

next in thread | previous in thread | raw e-mail | index | archive | help
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



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2B7WWSenB6bwvtVfyFvgE-ebz3LgcMMrhHqUkOvL1wA8vRpvtA>