From: Ian Lance Taylor <ian@wasabisystems.com>
To: Adrian Bentley <adruab@voria.com>
Cc: gcc-help@gcc.gnu.org
Subject: Re: Weird optimization bug...?
Date: Sat, 05 Jun 2004 23:31:00 -0000 [thread overview]
Message-ID: <m3ekot4m6m.fsf@gossamer.airs.com> (raw)
In-Reply-To: <1086462579.11861.2.camel@localhost>
Adrian Bentley <adruab@voria.com> writes:
> Is there any pragma or the like to disable gcc optimizations around a
> certain part of a file?
No, I'm afraid not. The optimization options affect the entire file.
Ian
next prev parent reply other threads:[~2004-06-05 23:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-02 20:24 Adrian Bentley
2004-06-03 11:26 ` Eljay Love-Jensen
2004-06-03 17:24 ` Adrian Bentley
2004-06-03 18:37 ` Eljay Love-Jensen
2004-06-03 19:11 ` Adrian Bentley
2004-06-03 21:17 ` Adrian Bentley
2004-06-03 23:06 ` Adrian Bentley
2004-06-04 3:00 ` Ian Lance Taylor
2004-06-05 19:09 ` Adrian Bentley
2004-06-05 23:31 ` Ian Lance Taylor [this message]
2004-06-06 0:47 ` Ken Foskey
2004-06-05 20:21 ` Adrian Bentley
[not found] ` <m3aczh4m55.fsf@gossamer.airs.com>
2004-06-06 16:44 ` Adrian Bentley
2004-06-06 22:23 ` Ian Lance Taylor
2004-06-03 19:13 lrtaylor
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=m3ekot4m6m.fsf@gossamer.airs.com \
--to=ian@wasabisystems.com \
--cc=adruab@voria.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).