On 28/07/15 05:42, Jan Alexander Steffens wrote:
> On Mon, Jul 27, 2015 at 6:15 AM, Allan McRae wrote:
>> We have a couple of bugs open about our CFLAGS.
>>
>> 1) https://bugs.archlinux.org/task/44361 -Remove the no-op
>> --param=ssp-buffer-size=4 switch from CFLAGS
>> Since we moved from -fstack-
On 27/07, Jan Alexander Steffens wrote:
On Mon, Jul 27, 2015 at 6:15 AM, Allan McRae wrote:
We have a couple of bugs open about our CFLAGS.
1) https://bugs.archlinux.org/task/44361 -Remove the no-op
--param=ssp-buffer-size=4 switch from CFLAGS
Since we moved from -fstack-protector to -fstack-p
-fstack-check works very well on x86 and x86_64 but is quite buggy on
other architectures like ARM. I'm not quite sure if that was the point
being made though.
signature.asc
Description: OpenPGP digital signature
On Mon, Jul 27, 2015 at 6:15 AM, Allan McRae wrote:
> We have a couple of bugs open about our CFLAGS.
>
> 1) https://bugs.archlinux.org/task/44361 -Remove the no-op
> --param=ssp-buffer-size=4 switch from CFLAGS
> Since we moved from -fstack-protector to -fstack-protector-strong, this
> paramater
We have a couple of bugs open about our CFLAGS.
1) https://bugs.archlinux.org/task/44361 -Remove the no-op
--param=ssp-buffer-size=4 switch from CFLAGS
Since we moved from -fstack-protector to -fstack-protector-strong, this
paramater is unused and can be removed.
2) https://bugs.archlinux.org/ta
On 12/04/14 17:52, Thomas Bächler wrote:
> Am 12.04.2014 09:22, schrieb Allan McRae:
>> Hi all,
>>
>> gcc-4.9 is due to be released on the 22nd. This brings a new stack
>> protection flag, -fstack-protector-strong. See this blog post for some
>> details [1].
>>
>> I would like to do two things wi
Am 12.04.2014 09:22, schrieb Allan McRae:
> Hi all,
>
> gcc-4.9 is due to be released on the 22nd. This brings a new stack
> protection flag, -fstack-protector-strong. See this blog post for some
> details [1].
>
> I would like to do two things with the release of gcc-4.9:
> 1) Add -fstack-prot
Hi all,
gcc-4.9 is due to be released on the 22nd. This brings a new stack
protection flag, -fstack-protector-strong. See this blog post for some
details [1].
I would like to do two things with the release of gcc-4.9:
1) Add -fstack-protector-strong to our CFLAGS
2) Rebuild all [core] packages
8 matches
Mail list logo