siddhesh

4 ms·

1.
How to improve application security using _FORTIFY_SOURCE=3(developers.redhat.com)
1 points by siddhesh 4y ago|0 comments
2.
Testing compiler and runtime changes with automated mass rebuilds(developers.redhat.com)
1 points by siddhesh 4y ago|1 comments
3.
by siddhesh 4y ago
Frederic Berat writes about the mass prebuilder he has been working on to test changes to compilers and toolchain components.
4.
by siddhesh 4y ago
It's not a runtime flag, you'll have to patch redhat-rpm-config to use _FORTIFY_SOURCE=3 instead of 2 and then build packages with it. Of course if you only want to build your application with _FORTIFY_SOURCE=3, you can do it righ
5.
by siddhesh 4y ago
Yes.
6.
by siddhesh 4y ago
It's on my TODO list. Watch out for Fedora change proposals for (hopefully) Fedora 38.
7.
by siddhesh 4y ago
OpenSUSE already enables it across the distribution; they were the first to do it. I believe Gentoo either already has or is in the process of doing it. I'll make a proposal for Fedora once I have a better idea of the code size and per
8.
by siddhesh 5y ago
You mean, like this? https://imgur.com/a/unKuOoK Snark aside, most text based editors have some giveaway or another. Even the GUI ones show syntax highlighting quirks that show that something is wrong. This is only re
9.
by siddhesh 7y ago
That was my second fallback until a couple of months ago and in fact I did some work for openresty too for luajit. Openresty luajit2 however has a bunch of extensions that are incompatible with Lua and luajit, making it unsuitable as the st
10.
by siddhesh 7y ago
The v2.1 branch of moonjit specifically aims to remain "luajit-like" in the sense that it is the explicit goal to make sure we don't add incompatible features and we definitely don't make it so that if Mike Pall decides
11.
by siddhesh 7y ago
FWIW, if RaptorJIT had not ripped out arm64, I would have ended up recommending replacing Luajit with RaptorJIT in Fedora and not bothered with forking moonjit.
12.
by siddhesh 12y ago
> 17:24:53 < derf> They reset the rounding modes on entrance and exit of expf(), for example, regardless of whether or not they're already correctly set up. I fixed this around the same time I worked on the mp improvements: co
13.
by siddhesh 12y ago
These are all the changes I made in math during 2.18. They're almost all mp stuff with some code cleanup thrown in. git log --author=siddhesh release/2.18/master -- sysdeps/ieee754/dbl-64
14.
by siddhesh 12y ago
We have had this in our todo list for a while. The leading idea currently is to provide compiler selectable function variants that don't fall into the multiple precision abyss. The biggest challenge here is to come up with data about a
15.
by siddhesh 12y ago
Yes the link is incorrect. I am working on getting that fixed.
16.
by siddhesh 12y ago
The crlibm code is terrible to read and hence maintain. I had considered including crlibm too during my work but decided against it because it would be a lot more work. Also, crlibm functions are provably correctly rounded only for univari