* Serge Guelton:
> https://clang.llvm.org/docs/SafeStack.html looks like a decent choice.
“Linking a DSO with SafeStack is not currently supported.”
I also don't see any discussion of debugging support.
Thanks,
Florian
___
devel mailing list -- devel@l
On Thu, Jan 03, 2019 at 12:31:50PM -0800, Tom Stellard wrote:
> On 01/03/2019 12:28 PM, Carlos O'Donell wrote:
> > On 1/3/19 2:49 PM, Michael Cronenworth wrote:
> >> Part of Fedora's default C/CXX flags include -fstack-clash-protection
> >> but clang does not support this flag and has until a few w
* Michael Cronenworth:
> On 1/3/19 3:16 PM, Stephen Gallagher wrote:
>> "Compliant with Fedora policy" == gcc right now.
>>
>> Fromhttps://fedoraproject.org/wiki/Packaging:Guidelines#Compiler
>> "Fedora uses gcc as the compiler (for all languages that gcc
>> supports). Packages may only build with
On Thu, Jan 3, 2019 at 4:23 PM Michael Cronenworth wrote:
>
> On 1/3/19 3:16 PM, Stephen Gallagher wrote:
> > "Compliant with Fedora policy" == gcc right now.
> >
> > Fromhttps://fedoraproject.org/wiki/Packaging:Guidelines#Compiler
> > "Fedora uses gcc as the compiler (for all languages that gcc
>
* Michael Cronenworth:
> On 1/3/19 2:31 PM, Tom Stellard wrote:
>> The recommended solution for now is to filter out flags that clang does
>> not support.
>
> I'm aware of how to adjust flags, but if everyone wants to dump gcc
> and adopt clang (I'm not one of those buying-in) wouldn't you want to
On 1/3/19 3:16 PM, Stephen Gallagher wrote:
"Compliant with Fedora policy" == gcc right now.
Fromhttps://fedoraproject.org/wiki/Packaging:Guidelines#Compiler
"Fedora uses gcc as the compiler (for all languages that gcc
supports). Packages may only build with an alternative compiler to gcc
if ups
On Thu, Jan 3, 2019 at 3:55 PM Michael Cronenworth wrote:
>
> On 1/3/19 2:31 PM, Tom Stellard wrote:
> > The recommended solution for now is to filter out flags that clang does
> > not support.
>
> I'm aware of how to adjust flags, but if everyone wants to dump gcc and adopt
> clang
> (I'm not on
On 1/3/19 2:31 PM, Tom Stellard wrote:
The recommended solution for now is to filter out flags that clang does
not support.
I'm aware of how to adjust flags, but if everyone wants to dump gcc and adopt clang
(I'm not one of those buying-in) wouldn't you want to make it 1) easy and 2)
complian
On 01/03/2019 12:28 PM, Carlos O'Donell wrote:
> On 1/3/19 2:49 PM, Michael Cronenworth wrote:
>> Part of Fedora's default C/CXX flags include -fstack-clash-protection
>> but clang does not support this flag and has until a few weeks ago[1]
>> silently ignored the flag.
>>
>> What are clang apps wh
On 1/3/19 2:49 PM, Michael Cronenworth wrote:
> Part of Fedora's default C/CXX flags include -fstack-clash-protection
> but clang does not support this flag and has until a few weeks ago[1]
> silently ignored the flag.
>
> What are clang apps who use Fedora's default flags supposed to do?
> Are th
Part of Fedora's default C/CXX flags include -fstack-clash-protection but clang does
not support this flag and has until a few weeks ago[1] silently ignored the flag.
What are clang apps who use Fedora's default flags supposed to do? Are there clang
default flag macros?
Thanks,
Michael
[1] h
11 matches
Mail list logo
