public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "falk at debian dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/14809] performance depends on allocation methods Date: Thu, 01 Apr 2004 13:27:00 -0000 [thread overview] Message-ID: <20040401132726.25703.qmail@sources.redhat.com> (raw) In-Reply-To: <20040401120607.14809.boeck@fhi-berlin.mpg.de> ------- Additional Comments From falk at debian dot org 2004-04-01 13:27 ------- It probably depends on alignment of the pointers relative to cache lines. You should look at alignment. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=14809
next prev parent reply other threads:[~2004-04-01 13:27 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-04-01 12:06 [Bug c++/14809] New: " boeck at fhi-berlin dot mpg dot de 2004-04-01 13:25 ` [Bug c++/14809] " pinskia at gcc dot gnu dot org 2004-04-01 13:27 ` falk at debian dot org [this message] 2004-04-01 15:13 ` boeck at sfhingx dot de 2004-04-01 15:34 ` falk at debian dot org 2004-04-01 16:00 ` bangerth at dealii dot org 2004-05-03 17:26 ` aleks at physik dot tu-berlin dot de 2004-05-03 18:23 ` bangerth at dealii 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=20040401132726.25703.qmail@sources.redhat.com \ --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).