https://gcc.gnu.org/bugzilla/show_bug.cgi?id=111070
PaX Team changed:
What|Removed |Added
CC||pageexec at gmail dot com
--- Comment #8
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96503
PaX Team changed:
What|Removed |Added
CC||pageexec at gmail dot com
--- Comment #2
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105171
--- Comment #14 from PaX Team ---
(In reply to Jakub Jelinek from comment #13)
> As has been said, we can't retroactively change released compilers from the
> last 2 decades. And going forward, I think walking the save_decoded_options
> is
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105171
--- Comment #12 from PaX Team ---
(In reply to Jakub Jelinek from comment #11)
> I think kernel requires gcc >= 5.1 anyway.
there's more than one kernel version in active use and under
development/support, even by upstream, not to mention
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105171
--- Comment #9 from PaX Team ---
(In reply to Andrew Pinski from comment #7)
> I think there might be a way to check if the option -frandom-seed was passed
> and that might be a better option for your usage anyways. You should check
> the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=105171
--- Comment #6 from PaX Team ---
(In reply to Andrew Pinski from comment #5)
> > So that I can decide whether I am allowed to do things totally randomly
> > or if I must follow some sort of seeded determinism.
>
> That is almost always the
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=104973
--- Comment #3 from PaX Team ---
(In reply to Andrew Pinski from comment #1)
> Can you attach what is inside cpugen.go?
i'm one of the original bug reproducers, this is what i get here:
