public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "pinskia at physics dot uc dot edu" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug optimization/9567] Using struct fields produces worse code than stand-alone vars. Date: Sun, 27 Jul 2003 20:56:00 -0000 [thread overview] Message-ID: <20030727205626.32213.qmail@sources.redhat.com> (raw) In-Reply-To: <20030204121601.9567.osv@javad.ru> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=9567 pinskia at physics dot uc dot edu changed: What |Removed |Added ---------------------------------------------------------------------------- Status|WAITING |NEW Last reconfirmed|2003-05-26 00:17:57 |2003-07-27 20:56:25 date| | ------- Additional Comments From pinskia at physics dot uc dot edu 2003-07-27 20:56 ------- I can provide one: struct A { char const* src; char* dest; }; void f1(char const** src, char** dest) { A a; a.src= *src; a.dest= *dest; for(int i = 0; i < 10; ++i) *++a.dest = *++a.src; *src = a.src; *dest= a.dest; } void f2(char const** src1, char** dest1) { char const* src = *src1; char* dest = *dest1; for(int i = 0; i < 10; ++i) *++dest = *++src; *src1 = src; *dest1 = dest; }
next prev parent reply other threads:[~2003-07-27 20:56 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <20030204121601.9567.osv@javad.ru> 2003-05-26 0:27 ` pinskia@physics.uc.edu 2003-05-26 7:15 ` falk@debian.org 2003-06-20 21:41 ` dhazeghi at yahoo dot com 2003-07-27 20:56 ` pinskia at physics dot uc dot edu [this message] 2003-11-10 8:14 ` pinskia at gcc dot gnu dot org 2003-11-15 8:25 ` pinskia at gcc dot gnu dot org 2003-12-01 4:18 ` pinskia at gcc dot gnu dot org 2004-03-03 6:09 ` pinskia at gcc dot gnu dot org 2004-05-13 15:14 ` [Bug optimization (tree-ssa)/9567] " pinskia at gcc dot gnu 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=20030727205626.32213.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).