public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "kevin at planetsaphire dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/23605] memset() Optimization on x86-32 bit Date: Sun, 28 Aug 2005 22:18:00 -0000 [thread overview] Message-ID: <20050828215804.7908.qmail@sourceware.org> (raw) In-Reply-To: <20050828200424.23605.kevin@planetsaphire.com> ------- Additional Comments From kevin at planetsaphire dot com 2005-08-28 21:58 ------- (In reply to comment #6) > inlining memset is not an optimization as most OS's memsets are better than the inlined version, using > sse registers,etc. I have finished reviewing over the glibc memset.* source files for the 32-bit Intel platforms, simply because every one using Linux is using glibc as the "libc". I find that SSE (nor even MMX) is used in the 32-bit implementations of memset. I think it is best to change this bug into an enhancement for the next available GCC branch. The reason for this change is because of a few reasons: 1. Fedora Core 3 (the distro installed on my computer) does not install the i686 binaries of glibc during install; rather, it installs the i386 version. 2. You are right about systems having better memset()s, though considering the widespread use of glibc, most implementations do not utilize SSE, MMX, etc. Maybe the memset() optimization can be turned on by the use of a new flag? After all, the i386 build of glibc does not include the use of instructions that can possibly be used on i686. In addition, there may be a few circumstances where the user may not want to use the i686 build, such as debugging, apps that require the i386 build (perhaps to get around a few glibc bugs), and hardware processor issues with other functions in glibc. I hope the GCC staff and the steering committee reviews over this possible enhancement seriously. The optimization would allow the user to get around slower code in certain situations when it comes to using memset(). -- What |Removed |Added ---------------------------------------------------------------------------- Severity|minor |enhancement Status|RESOLVED |UNCONFIRMED Priority|P2 |P1 Resolution|INVALID | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23605
next prev parent reply other threads:[~2005-08-28 21:58 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-08-28 20:08 [Bug c/23605] New: " kevin at planetsaphire dot com 2005-08-28 20:16 ` [Bug target/23605] " pinskia at gcc dot gnu dot org 2005-08-28 20:26 ` kevin at planetsaphire dot com 2005-08-28 20:28 ` kevin at planetsaphire dot com 2005-08-28 20:34 ` pinskia at gcc dot gnu dot org 2005-08-28 20:37 ` kevin at planetsaphire dot com 2005-08-28 20:45 ` pinskia at gcc dot gnu dot org 2005-08-28 22:18 ` kevin at planetsaphire dot com [this message] 2005-08-28 23:00 ` pinskia at gcc dot gnu dot org 2005-08-28 23:03 ` pinskia at gcc dot gnu dot org 2005-08-28 23:25 ` ian at airs dot com 2005-08-28 23:42 ` ian at airs dot com 2005-08-29 0:36 ` kevin at planetsaphire dot com 2005-08-29 0:49 ` kevin at planetsaphire dot com [not found] <bug-23605-11252@http.gcc.gnu.org/bugzilla/> 2005-11-02 17:16 ` pinskia at gcc dot gnu dot org 2006-09-18 1:45 ` pinskia at gcc dot gnu dot org [not found] <bug-23605-4@http.gcc.gnu.org/bugzilla/> 2012-01-11 14:21 ` rguenth at gcc dot gnu.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=20050828215804.7908.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).