public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "janis at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/23449] vortex fails without -fno-strict-aliasing
Date: Wed, 07 Sep 2005 21:07:00 -0000	[thread overview]
Message-ID: <20050907210711.21063.qmail@sourceware.org> (raw)
In-Reply-To: <20050817234924.23449.janis@gcc.gnu.org>


------- Additional Comments From janis at gcc dot gnu dot org  2005-09-07 21:07 -------
The code in mem*.[ch] is much messier than I originally thought.  There are
lots of casts in assignments of pointer variables.  The macros in mem00.h
starting with Unit_Size, which are used in both lvalues and rvalues,
dereference through pointer casts.

I'm no longer planning to suggest a fix to SPEC.  The code in vortex violates
aliasing rules and any fix would not be portable C; we'll need to work around
it by compiling with -fno-strict-aliasing until someone comes up with a better
solution.

Closing this PR as INVALID.

-- 
           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


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


  parent reply	other threads:[~2005-09-07 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-17 23:53 [Bug tree-optimization/23449] New: " janis at gcc dot gnu dot org
2005-09-02 20:34 ` [Bug tree-optimization/23449] " janis at gcc dot gnu dot org
2005-09-07 21:07 ` janis at gcc dot gnu dot org [this message]
     [not found] <bug-23449-4503@http.gcc.gnu.org/bugzilla/>
2007-10-12 10:16 ` ubizjak at gmail dot com
2009-01-15 19:32 ` raksit at google dot com

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=20050907210711.21063.qmail@sourceware.org \
    --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).