[Bug java/82263] New: java multilib -m32 version is using 64 bit include and lib, _GStaticAssertCompileTimeAssertion_0

2017-09-19 Thread gccbugzilla.severach at spamgourmet dot com
Severity: normal Priority: P3 Component: java Assignee: unassigned at gcc dot gnu.org Reporter: gccbugzilla.severach at spamgourmet dot com Target Milestone: --- Snapshot 6-20170913 fixed all glibc 2.26 issues except for the -m32 multilib version of

[Bug java/82263] java multilib -m32 version is using 64 bit include and lib, _GStaticAssertCompileTimeAssertion_0

2017-09-20 Thread gccbugzilla.severach at spamgourmet dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82263 --- Comment #2 from Chris Severance --- I'm building gcc 6.4.1 6-20170913 with gcc 7.2.0. The -m32 version of java does not build.

[Bug c/81400] New: Stack smashing not caught by stack protector strong and allowing me to stack smash

2017-07-11 Thread gccbugzilla.severach at spamgourmet dot com
Severity: normal Priority: P3 Component: c Assignee: unassigned at gcc dot gnu.org Reporter: gccbugzilla.severach at spamgourmet dot com Target Milestone: --- Created attachment 41720 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41720&action=edi

[Bug middle-end/81400] Stack smashing not caught by stack protector strong and allowing me to stack smash

2017-07-12 Thread gccbugzilla.severach at spamgourmet dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81400 --- Comment #3 from Chris Severance --- Unless there's a security reason 0 should never be used as a canary value. Errant \0 should be caught 100% of the time. When I built malloc canaries for NPPTextFX I expressly avoided \0. data[SMASH_ALIGN]=