public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "wvangulik at xs4all dot nl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/34737] missed optimization, foo(p); p++ is better then foo(p++)
Date: Fri, 11 Jan 2008 08:59:00 -0000 [thread overview]
Message-ID: <20080111081727.24387.qmail@sourceware.org> (raw)
In-Reply-To: <bug-34737-14966@http.gcc.gnu.org/bugzilla/>
------- Comment #1 from wvangulik at xs4all dot nl 2008-01-11 08:17 -------
Created an attachment (id=14920)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=14920&action=view)
Test case showing the three cases
Compile using -fno-line.
For the AVR I used: avr-gcc -Wall -Os -fno-inline -mmcu=avr5 --save-temps
main.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=34737
next prev parent reply other threads:[~2008-01-11 8:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-11 8:58 [Bug c/34737] New: " wvangulik at xs4all dot nl
2008-01-11 8:59 ` wvangulik at xs4all dot nl [this message]
2008-01-11 10:19 ` [Bug tree-optimization/34737] Inefficient gimplification of post-modified function arguments, TER doesn't do its work rguenth at gcc dot gnu dot org
2008-01-11 11:48 ` [Bug tree-optimization/34737] Scheduling of post-modified function arguments is not good pinskia at gcc dot gnu dot org
2009-06-24 7:42 ` steven at gcc dot gnu dot org
2009-06-24 9:08 ` rguenther at suse dot de
2010-09-13 11:38 ` abnikant dot singh at atmel dot com
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=20080111081727.24387.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: link
Be 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).