From: =?ISO-8859-2?Q?V?clav_Haisman?= <HAISMAV@feld.cvut.cz>
To: gcc-help@gcc.gnu.org
Subject: question about -fstrict-aliasing
Date: Wed, 02 Feb 2000 02:32:00 -0000 [thread overview]
Message-ID: <418DF53716@FELIS.FELD.CVUT.CZ> (raw)
hi there,
is there any way how to disable/enable -fstrict-aliasing optimization
for parts of code?
V.Haisman@sh.cvut.cz
WARNING: multiple messages have this Message-ID
From: =?ISO-8859-2?Q?V?clav_Haisman?= <HAISMAV@feld.cvut.cz>
To: gcc-help@gcc.gnu.org
Subject: question about -fstrict-aliasing
Date: Sat, 01 Apr 2000 00:00:00 -0000 [thread overview]
Message-ID: <418DF53716@FELIS.FELD.CVUT.CZ> (raw)
Message-ID: <20000401000000.jzR9_FVgOSQw4H8JMNw1pnwb9v9nsaOTh7z5j4E-XCw@z> (raw)
hi there,
is there any way how to disable/enable -fstrict-aliasing optimization
for parts of code?
V.Haisman@sh.cvut.cz
next reply other threads:[~2000-02-02 2:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-02 2:32 =?ISO-8859-2?Q?V?clav_Haisman?= [this message]
2000-04-01 0:00 ` =?ISO-8859-2?Q?V?clav_Haisman?=
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=418DF53716@FELIS.FELD.CVUT.CZ \
--to=haismav@feld.cvut.cz \
--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).