public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug other/52609] -Wstrict-aliasing / missed diagnostics
Date: Sat, 17 Mar 2012 22:03:00 -0000	[thread overview]
Message-ID: <bug-52609-4-0E3YjkEAjK@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52609-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52609

--- Comment #1 from Andrew Pinski <pinskia at gcc dot gnu.org> 2012-03-17 21:57:19 UTC ---
>accessing unsigned* via float* looks buggy

It does not have to be if the original argument was originally of type float.
Aliasing is not about type of pointers but the type which is used to access and
such.


  reply	other threads:[~2012-03-17 21:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-17 12:30 [Bug other/52609] New: " pluto at agmk dot net
2012-03-17 22:03 ` pinskia at gcc dot gnu.org [this message]
2012-03-18 12:53 ` [Bug other/52609] " pluto at agmk dot net
2012-03-19 10:57 ` rguenth at gcc dot gnu.org
2012-10-23 18:47 ` manu at gcc dot gnu.org

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=bug-52609-4-0E3YjkEAjK@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).