From: Jonathan Larmour <jlarmour@redhat.com>
To: Doug Fraser <dfraser@photuris.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] Optimizations and bad code
Date: Mon, 23 Jul 2001 12:36:00 -0000 [thread overview]
Message-ID: <3B5C7C9E.8558FBC6@redhat.com> (raw)
In-Reply-To: <E2D27064CD59574F88D05AEF5728396D4453FB@PH01SRV02.photuris.com>
Doug Fraser wrote:
> That the arm-elf compiler only increments 'i' by
> one for a particular optimizer setting is a defect, and badly
> formed source code is no excuse for erroneous object code.
Not true at all. Badly formed source code is a perfectly valid reason to
produce code that doesn't do what the programmer expects. After all in
situations like this, how can the compiler guess what the programmer
expects. Maybe it should warn though - I don't know if it does (at default
level or at -Wall).
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
Come to the Red Hat TechWorld open source conference in Brussels!
Keynotes, techie talks and exhibitions http://www.redhat-techworld.com/
next prev parent reply other threads:[~2001-07-23 12:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-23 9:47 Doug Fraser
2001-07-23 12:36 ` Jonathan Larmour [this message]
[not found] <E2D27064CD59574F88D05AEF5728396D4453FD@PH01SRV02.photuris.com>
2001-07-24 6:23 ` Jonathan Larmour
-- strict thread matches above, loose matches on Subject: below --
2001-07-24 1:07 rob.wj.jansen
2001-07-23 0:58 rob.wj.jansen
2001-07-23 6:32 ` Gary Thomas
2001-07-23 9:31 ` Trenton D. Adams
2001-07-20 10:31 Trenton D. Adams
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=3B5C7C9E.8558FBC6@redhat.com \
--to=jlarmour@redhat.com \
--cc=dfraser@photuris.com \
--cc=ecos-discuss@sourceware.cygnus.com \
/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).