public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: jsm28@gcc.gnu.org
To: cchen@corelation.com, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
	jsm28@cam.ac.uk, nobody@gcc.gnu.org
Subject: Re: c/2419: GCC 2.96 FP bit manipulation snafu
Date: Fri, 22 Jun 2001 03:57:00 -0000	[thread overview]
Message-ID: <20010622105723.28986.qmail@sourceware.cygnus.com> (raw)

Synopsis: GCC 2.96 FP bit manipulation snafu

State-Changed-From-To: open->closed
State-Changed-By: jsm28
State-Changed-When: Fri Jun 22 03:57:22 2001
State-Changed-Why:
    The program appears to act as you expect with GCC 3.0, though
    you should be using -fno-strict-aliasing since it doesn't
    follow ISO C aliasing rules.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2419&database=gcc


             reply	other threads:[~2001-06-22  3:57 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-22  3:57 jsm28 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-28 12:46 cchen

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=20010622105723.28986.qmail@sourceware.cygnus.com \
    --to=jsm28@gcc.gnu.org \
    --cc=cchen@corelation.com \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jsm28@cam.ac.uk \
    --cc=nobody@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).