public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/64200] ICE: in decide_alg, at config/i386/i386.c:24510 with -mmemcpy-strategy=libcall:-1:align -minline-stringops-dynamically Date: Fri, 05 Dec 2014 20:15:00 -0000 [thread overview] Message-ID: <bug-64200-4-r0GiBmk20H@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-64200-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64200 H.J. Lu <hjl.tools at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|UNCONFIRMED |NEW Last reconfirmed| |2014-12-05 CC| |ubizjak at gmail dot com Target Milestone|--- |5.0 Ever confirmed|0 |1 --- Comment #1 from H.J. Lu <hjl.tools at gmail dot com> --- GCC manual says: '-minline-stringops-dynamically' For string operations of unknown size, use run-time checks with inline code for small blocks and a library call for large blocks. Why are there gcc_assert (alg != libcall); if (TARGET_INLINE_STRINGOPS_DYNAMICALLY) *dynamic_check = max; return alg; libcall should be fine for TARGET_INLINE_STRINGOPS_DYNAMICALLY.
next prev parent reply other threads:[~2014-12-05 20:15 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-12-05 18:48 [Bug target/64200] New: " zsojka at seznam dot cz 2014-12-05 20:15 ` hjl.tools at gmail dot com [this message] 2014-12-06 11:33 ` [Bug target/64200] " hjl at gcc dot gnu.org 2014-12-08 13:35 ` rguenth at gcc dot gnu.org 2014-12-14 13:05 ` hjl at gcc dot gnu.org 2014-12-14 13:06 ` hjl.tools at gmail dot com
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=bug-64200-4-r0GiBmk20H@http.gcc.gnu.org/bugzilla/ \ --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).