public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ebotcazou at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/44993] [4.6 regression] sparc64-linux bootstrap broken
Date: Tue, 27 Jul 2010 20:16:00 -0000	[thread overview]
Message-ID: <20100727201557.17560.qmail@sourceware.org> (raw)
In-Reply-To: <bug-44993-7210@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from ebotcazou at gcc dot gnu dot org  2010-07-27 20:15 -------
Introduced by the fix for PR middle-end/44790:

2010-07-07  Richard Guenther  <rguenther@suse.de>

        PR middle-end/44790
        * expr.c (expand_expr_real_1): Go the POINTER_PLUS_EXPR path
        for expanding the constant offset for MEM_REFs.

The problem is that:

  name = MEM[(struct
exp_ch3__make_predefined_primitive_specs__B_99__stream_op_tss_names___PAD
*)D.14526_1156 + 4294967296B];

is expanded into

        sethi   %hi(stream_op_tss_names.6060+4294967296), %l2
        or      %l2, %lo(stream_op_tss_names.6060+4294967296), %l2

which overflows since sethi is a 32-bit operator.

Going through POINTER_PLUS_EXPR to expand a const addresss apparently bypasses
checks for valid addresses in the back-end.


-- 


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


  parent reply	other threads:[~2010-07-27 20:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-19 16:14 [Bug bootstrap/44993] New: " laurent at guerby dot net
2010-07-19 21:04 ` [Bug bootstrap/44993] " mikpe at it dot uu dot se
2010-07-24 21:43 ` ebotcazou at gcc dot gnu dot org
2010-07-24 21:44 ` ebotcazou at gcc dot gnu dot org
2010-07-27 20:16 ` ebotcazou at gcc dot gnu dot org [this message]
2010-07-28  7:45 ` [Bug middle-end/44993] " ebotcazou at gcc dot gnu dot org
2010-07-28  7:47 ` ebotcazou 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=20100727201557.17560.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).