++
Assignee: unassigned at gcc dot gnu.org
Reporter: ago at gentoo dot org
Target Milestone: ---
Hello All.
During the fuzz of podofo I hit this warning:
/usr/lib/gcc/x86_64-pc-linux-gnu/4.9.4/include/g++-v4/bits/ios_base.h:96:24:
runtime error: load of value 4294967035, which
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112635
Agostino Sarubbo changed:
What|Removed |Added
Status|UNCONFIRMED |RESOLVED
Resolution|---
: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: ago at gentoo dot org
Target Milestone: ---
Historically, distro like Gentoo Hardened, used patches to make gcc compile by
default with pie/ssp.
After a lot of years
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112897
--- Comment #2 from Agostino Sarubbo ---
I don't know if I was able to provide the concept, but in other words if we
know that something like -fstack-clash-protection is widely used nowadays, it
make no sense rebase patches for 10 years and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=112635
--- Comment #2 from Agostino Sarubbo ---
(In reply to Richard Biener from comment #1)
> Yep, GCC fixes the code for you by eliding 'buf'. That's perfectly OK though
> since the code invokes undefined behavior.
>
> I'm inclined to close this
Priority: P3
Component: libgcc
Assignee: unassigned at gcc dot gnu.org
Reporter: ago at gentoo dot org
Target Milestone: ---
If this is a known thing, please forgive me.
I was playing with the stack-smash protection and this is what I have found.
Please
Severity: normal
Priority: P3
Component: other
Assignee: unassigned at gcc dot gnu.org
Reporter: ago at gentoo dot org
Target Milestone: ---
man gcc says:
-fcf-protection=[full|branch|return|none|check]
However, at runtime, you can use -fcf
