public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/36079] cld instruction is not emitted anymore. Date: Tue, 29 Apr 2008 13:15:00 -0000 [thread overview] Message-ID: <20080429131502.32336.qmail@sourceware.org> (raw) In-Reply-To: <bug-36079-1649@http.gcc.gnu.org/bugzilla/> ------- Comment #1 from ubizjak at gmail dot com 2008-04-29 13:15 ------- Since there are many workarounds for this problem I think that this problem should be fixed elsewhere by either (a) fixing the kernel or (b) fixing the application that is affected by the problem a) A two-liner patch to the kernel. This is the approach that major distribution have taken. b) The fix is to add explicit cld at the beginning of the function that can be called from exception handler and uses string operations. Due to the nature of the problem, it is very unlikely that this problem will hit real word applications. OTOH, cld instruction has non-negligible performance impact. Adding -mcld to compile flags in order to emit cld at the beginning of every function that uses stringops will introduce certain performance hit. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36079
next prev parent reply other threads:[~2008-04-29 13:15 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-04-29 12:53 [Bug target/36079] New: " ubizjak at gmail dot com 2008-04-29 13:15 ` ubizjak at gmail dot com [this message] 2008-04-29 13:37 ` [Bug target/36079] " cnstar9988 at gmail dot com 2008-04-29 14:47 ` [Bug target/36079] [4.3/4.4 Regression] " rguenth at gcc dot gnu dot org 2008-05-05 15:49 ` jsm28 at gcc dot gnu dot org 2008-05-20 5:47 ` ubizjak at gmail dot com 2008-05-20 7:09 ` cnstar9988 at gmail dot com 2008-05-20 8:49 ` cnstar9988 at gmail dot com 2008-05-20 12:52 ` ubizjak at gmail dot com 2008-05-20 15:18 ` cnstar9988 at gmail dot com 2008-05-20 15:25 ` cnstar9988 at gmail dot com 2008-05-20 15:28 ` rguenther at suse dot de 2008-05-21 8:55 ` uros at gcc dot gnu dot org 2008-05-22 2:42 ` cnstar9988 at gmail dot com 2008-05-23 7:54 ` uros at gcc dot gnu dot org 2008-05-23 8:40 ` ubizjak at gmail dot com 2008-06-10 10:08 ` cnstar9988 at gmail dot com 2008-06-10 10:57 ` rguenther at suse dot de
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=20080429131502.32336.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).