public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: "Paul Edwards" <mutazilah@gmail.com>
To: "Richard Guenther" <richard.guenther@gmail.com>
Cc: <gcc@gcc.gnu.org>
Subject: Re: i370 port - music/sp - possible generic gcc problem
Date: Sun, 29 Nov 2009 14:31:00 -0000	[thread overview]
Message-ID: <21C621DE1F0D4A7193A78C4FBEC7BD59@Paullaptop> (raw)

Latest information - 

> Ok, based on this, I traced it back further:
> 
> rtx
> gen_rtx_fmt_e0 (code, mode, arg0)
>     RTX_CODE code;
>     enum machine_mode mode;
>     rtx arg0;
> {
>  rtx rt;
>  rt = ggc_alloc_rtx (2);
>  memset (rt, 0, sizeof (struct rtx_def) - sizeof (rtunion));

The request for 2 (I guess, rtx's) results in a malloc for 65536
bytes, so presumably each rtx is 32k.  It appears that only the 
single byte at offset 47072 needs to be initialized to some
appropriate value (I found that x'08' and x'81' also work, and
I am still experimenting on that) in order to circumvent the 
problem of garbage code generation.

> rtx
> gen_rtx_MEM (mode, addr)
>     enum machine_mode mode;
>     rtx addr;
> {
>  rtx rt = gen_rtx_raw_MEM (mode, addr);
> 
>  /* This field is not cleared by the mere allocation of the rtx, so
>     we clear it here.  */
>  MEM_ATTRS (rt) = 0;
> 
>  return rt;
> }

I wonder if another field like the above also needs to be
initialized?  Or maybe the same field, but it needs to be
for the second rtx?

I will try to see if I can map that offset onto a meaningful variable.

BFN.  Paul.

             reply	other threads:[~2009-11-29 14:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-29 14:31 Paul Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-11-29  7:57 Paul Edwards
2009-11-24 14:05 i370 port - 3.4.6 to 4.4 upgrade attempt Ulrich Weigand
2009-11-28 15:14 ` i370 port - music/sp - possible generic gcc problem Paul Edwards
2009-11-28 16:03   ` Richard Guenther
2009-11-28 16:35     ` Paul Edwards
2009-11-28 17:03       ` Richard Guenther
2009-11-28 23:44         ` Paul Edwards

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=21C621DE1F0D4A7193A78C4FBEC7BD59@Paullaptop \
    --to=mutazilah@gmail.com \
    --cc=gcc@gcc.gnu.org \
    --cc=richard.guenther@gmail.com \
    /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).