public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/24406] EQUIVALENCE broken in 32-bit code with optimization -O2
Date: Sun, 23 Oct 2005 22:52:00 -0000	[thread overview]
Message-ID: <20051023225231.25061.qmail@sourceware.org> (raw)
In-Reply-To: <bug-24406-10567@http.gcc.gnu.org/bugzilla/>



------- Comment #5 from pinskia at gcc dot gnu dot org  2005-10-23 22:52 -------
Confirmed, fortran front-end needs to do something similar to the C front-end
in c-common.c/c_common_get_alias_set:

  /* Permit type-punning when accessing a union, provided the access
     is directly through the union.  For example, this code does not
     permit taking the address of a union member and then storing
     through it.  Even the type-punning allowed here is a GCC
     extension, albeit a common and useful one; the C standard says
     that such accesses have implementation-defined behavior.  */
  for (u = t;
       TREE_CODE (u) == COMPONENT_REF || TREE_CODE (u) == ARRAY_REF;
       u = TREE_OPERAND (u, 0))
    if (TREE_CODE (u) == COMPONENT_REF
        && TREE_CODE (TREE_TYPE (TREE_OPERAND (u, 0))) == UNION_TYPE)
      return 0;


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |pinskia at gcc dot gnu dot
                   |                            |org
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2005-10-23 22:52:31
               date|                            |


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


  parent reply	other threads:[~2005-10-23 22:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-17 11:10 [Bug fortran/24406] New: " mick at nag dot co dot uk
2005-10-17 11:29 ` [Bug fortran/24406] " pinskia at gcc dot gnu dot org
2005-10-17 11:30 ` pinskia at gcc dot gnu dot org
2005-10-17 18:01 ` kargl at gcc dot gnu dot org
2005-10-17 18:01 ` kargl at gcc dot gnu dot org
2005-10-23 22:52 ` pinskia at gcc dot gnu dot org [this message]
2005-11-01 20:20 ` tobi at gcc dot gnu dot org
2006-02-06 20:33 ` tkoenig at gcc dot gnu dot org
2006-02-06 20:56 ` [Bug rtl-optimization/24406] " tobi at gcc dot gnu dot org
2006-02-06 20:57 ` sgk at troutmask dot apl dot washington dot edu
2006-02-06 21:01 ` [Bug fortran/24406] " pinskia at gcc dot gnu dot org
2006-03-03 10:08 ` paul dot richard dot thomas at cea dot fr
2006-03-06 21:03 ` pinskia at gcc dot gnu dot org
2006-03-07  7:28 ` paul dot richard dot thomas at cea dot fr
2006-03-23  1:06 ` pinskia at gcc dot gnu dot org
2006-03-23  8:06 ` paul dot richard dot thomas at cea dot fr
2006-03-23 14:54   ` Andrew Pinski
2006-03-23 14:54 ` pinskia at physics dot uc dot edu
2006-04-23  6:07 ` pault at gcc dot gnu dot org
2006-04-24 10:13 ` mick at nag dot co dot uk

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=20051023225231.25061.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).