public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rguenther at suse dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/45623] [4.5/4.6 Regression] GCC 4.5.[01] breaks our ffi on Linux64. ABI break?
Date: Wed, 15 Sep 2010 13:56:00 -0000	[thread overview]
Message-ID: <20100915135618.21559.qmail@sourceware.org> (raw)
In-Reply-To: <bug-45623-18333@http.gcc.gnu.org/bugzilla/>



------- Comment #23 from rguenther at suse dot de  2010-09-15 13:56 -------
Subject: Re:  [4.5/4.6 Regression] GCC 4.5.[01]
 breaks our ffi on Linux64. ABI break?

On Wed, 15 Sep 2010, mh+gcc at glandium dot org wrote:

> ------- Comment #22 from mh+gcc at glandium dot org  2010-09-15 13:52 -------
> (In reply to comment #21)
> > For the original code?  Then your reduced testcase is different from the
> > original problem.
> 
> It doesn't work for the reduced testcase here, with gcc 4.5.1

It does fix the PTA problem (thus makes it work at -O1).  Still
fails at -O2 for some reason (but can't reproduce that on
the tip of the branch, only with the 4.5.1 release).  Alias-correct 
testcase:

#include <stdint.h>

extern void abort (void);

char *s1 = "foo";
char *s2 = "bar";

char **ss1 = &s1;

typedef union jsval_layout
{
    uint64_t asBits;
    char **ptr;
} jsval_layout;

int main()
{
  jsval_layout l, m;
  l.ptr = ss1;
  m.asBits = l.asBits;
  char ** data = m.ptr;
  *data = s2;
  if (s1 != s2)
    abort ();
  return 0;
}


-- 


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


  parent reply	other threads:[~2010-09-15 13:56 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-09 21:45 [Bug regression/45623] New: " tglek at mozilla dot com
2010-09-09 22:03 ` [Bug target/45623] " dwitte at mozilla dot com
2010-09-09 22:18 ` pinskia at gcc dot gnu dot org
2010-09-10  0:38 ` hjl dot tools at gmail dot com
2010-09-10  0:46 ` dwitte at mozilla dot com
2010-09-10  0:52 ` hjl dot tools at gmail dot com
2010-09-10  1:41 ` pinskia at gcc dot gnu dot org
2010-09-10  2:37 ` tglek at mozilla dot com
2010-09-10  2:57 ` hjl dot tools at gmail dot com
2010-09-15 11:45 ` mh+gcc at glandium dot org
2010-09-15 11:53 ` mh+gcc at glandium dot org
2010-09-15 12:05 ` mh+gcc at glandium dot org
2010-09-15 12:12 ` mh+gcc at glandium dot org
2010-09-15 12:16 ` rguenth at gcc dot gnu dot org
2010-09-15 12:31 ` [Bug tree-optimization/45623] [4.5/4.6 Regression] " rguenth at gcc dot gnu dot org
2010-09-15 12:47 ` mh+gcc at glandium dot org
2010-09-15 12:52 ` mh+gcc at glandium dot org
2010-09-15 13:04 ` rguenth at gcc dot gnu dot org
2010-09-15 13:14 ` mh+gcc at glandium dot org
2010-09-15 13:25 ` rguenth at gcc dot gnu dot org
2010-09-15 13:41 ` mh+gcc at glandium dot org
2010-09-15 13:50 ` rguenth at gcc dot gnu dot org
2010-09-15 13:52 ` mh+gcc at glandium dot org
2010-09-15 13:56 ` rguenther at suse dot de [this message]
2010-09-15 13:59 ` rguenth at gcc dot gnu dot org
2010-09-15 14:01 ` mh+gcc at glandium dot org
2010-09-16 11:06 ` rguenth at gcc dot gnu dot org
2010-09-16 11:07 ` [Bug tree-optimization/45623] [4.5 " rguenth at gcc dot gnu dot org
2010-09-17  9:09 ` rguenth at gcc dot gnu dot org
2010-09-20  8:34 ` rguenth at gcc dot gnu dot org
2010-09-20  8:34 ` rguenth at gcc dot gnu dot 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=20100915135618.21559.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).