public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "wbrana at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/54246] Bytemark FOURIER 54% slower with glibc 2.16 Date: Sun, 19 Aug 2012 08:20:00 -0000 [thread overview] Message-ID: <bug-54246-4-F03wk6zznl@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-54246-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=54246 wbrana <wbrana at gmail dot com> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|Bytemark FOURIER 54% slower |Bytemark FOURIER 54% slower |in X32 chroot |with glibc 2.16 --- Comment #2 from wbrana <wbrana at gmail dot com> 2012-08-19 08:20:06 UTC --- It isn't related to X32, but glibc 2.16. Bug submitted: http://sourceware.org/bugzilla/show_bug.cgi?id=14496
next prev parent reply other threads:[~2012-08-19 8:20 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-13 16:46 [Bug target/54246] New: Bytemark FOURIER 54% slower in X32 chroot wbrana at gmail dot com 2012-08-14 1:08 ` [Bug target/54246] " hjl.tools at gmail dot com 2012-08-19 8:20 ` wbrana at gmail dot com [this message] 2012-08-20 7:21 ` [Bug target/54246] Bytemark FOURIER 54% slower with glibc 2.16 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=bug-54246-4-F03wk6zznl@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).