From: "Phil Prentice" <PhilP@tsd.serco.com>
To: gcc-help@gcc.gnu.org
Subject: Help on 3.0.2
Date: Wed, 23 Jan 2002 01:26:00 -0000 [thread overview]
Message-ID: <sc4e81b6.061@tsd.serco.com> (raw)
Hi
For various reasons I have had to update to using the gcc 3.0.2 cross-compiler for vxWorks (i.e. m68-wrs-vxworks-gcc).
Are there any known problems with this version regarding optimisation? Code that I have built with 2.95.3 built and worked fine. As soon as I built it with 3.0.2 I started getting optimisation problems. It appears to be optimising my code even if I try and tell it not to (-O0). This is causing grief with drivers using interrupt routines. Also debug does not seem to be working as well as it use to....again is this due to unwanted optimisation?
I may need to go back to 2.95.3 and solve the warning problem that I had with that another way.
Thanks
Phil Prentice
reply other threads:[~2002-01-23 9:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=sc4e81b6.061@tsd.serco.com \
--to=philp@tsd.serco.com \
--cc=gcc-help@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).