public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/38454] [4.4 Regression] memcpy folding breaks -D_FORTIFY_SOURCE=2 protection Date: Tue, 09 Dec 2008 23:04:00 -0000 [thread overview] Message-ID: <20081209230308.7745.qmail@sourceware.org> (raw) In-Reply-To: <bug-38454-87@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from jakub at gcc dot gnu dot org 2008-12-09 23:03 ------- Subject: Bug 38454 Author: jakub Date: Tue Dec 9 23:01:15 2008 New Revision: 142617 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=142617 Log: PR middle-end/38454 * function.h (struct function): Add always_inline_functions_inlined. * ipa-inline.c (cgraph_early_inlining): Set it to true. * tree-optimize.c (execute_fixup_cfg): Likewise. * builtins.c (avoid_folding_inline_builtin): New function. (fold_call_expr): Don't optimize always_inline builtins before inlining. (fold_call_stmt): Likewise. (fold_builtin_call_array): Likewise. Don't call fold_builtin_varargs for BUILT_IN_MD builtins. * gcc.dg/memset-1.c: New test. * gcc.dg/memcpy-2.c: New test. Added: trunk/gcc/testsuite/gcc.dg/memcpy-2.c trunk/gcc/testsuite/gcc.dg/memset-1.c Modified: trunk/gcc/ChangeLog trunk/gcc/builtins.c trunk/gcc/function.h trunk/gcc/ipa-inline.c trunk/gcc/testsuite/ChangeLog trunk/gcc/tree-optimize.c -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38454
next prev parent reply other threads:[~2008-12-09 23:04 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-12-09 15:43 [Bug middle-end/38454] New: " jakub at gcc dot gnu dot org 2008-12-09 15:46 ` [Bug middle-end/38454] " jakub at gcc dot gnu dot org 2008-12-09 19:39 ` mmitchel at gcc dot gnu dot org 2008-12-09 23:04 ` jakub at gcc dot gnu dot org [this message] 2008-12-09 23:24 ` jakub at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20081209230308.7745.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).