public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Michael Matz <matz@suse.de>
To: Richard Guenther <richard.guenther@gmail.com>
Cc: "H.J. Lu" <hjl.tools@gmail.com>, Paolo Bonzini <bonzini@gnu.org>,
	gcc-patches@gcc.gnu.org
Subject: Re: PATCH: PR middle-end/48440: [4.7 Regression] FAIL: gcc.c-torture/compile/labels-3.c
Date: Thu, 07 Apr 2011 12:35:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.1104071423080.1989@wotan.suse.de> (raw)
In-Reply-To: <BANLkTik57razZYij6VXnQZ4JBE7QXpPTPQ@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1611 bytes --]

Hi,

On Thu, 7 Apr 2011, Richard Guenther wrote:

> > 5600      newx = simplify_subreg (outermode, op, innermode, byte);
> > (gdb) f 1
> > #1  0x0000000000708494 in expand_expr_real_2 (ops=0x7fffffffb0c0, target=0x0,
> >    tmode=VOIDmode, modifier=EXPAND_INITIALIZER)
> >    at /export/gnu/import/git/gcc-x32/gcc/expr.c:7366
> > 7366                op0 = simplify_gen_subreg (mode, op0, inner_mode,
> > (gdb) call debug_tree (treeop0)
> >  <addr_expr 0x7ffff0a78d50
> >    type <pointer_type 0x7ffff0b83f18
> >        type <void_type 0x7ffff0b83e70 void VOID
> >            align 8 symtab 0 alias set -1 canonical type 0x7ffff0b83e70
> >            pointer_to_this <pointer_type 0x7ffff0b83f18>>
> >        sizes-gimplified public unsigned SI
> >    arg 0 <label_decl 0x7ffff0b7b400 l2 type <void_type 0x7ffff0b83e70 void>
> > (gdb) call debug_rtx (op0)
> > (label_ref/v:DI 22)
> > (gdb)
> >
> 
> First I wonder what CONSTANT_P object we arrive with here (it looks like
> something unfolded, given that we likely came here with a NOP_EXPR).

The CONSTANT_P object is the '(label_ref/v:DI 22)'.  Not only CONST_INT 
are CONSTANT_P, also some others (symbol_ref too).  Those might have a 
mode.  Here the label_ref has DImode, but the pointer type in trees points 
to an SImode.  The latter makes sense, because that's what ptr_mode is for 
HJs target.

HJ: you'll need to tell us what you mean with 'breaks 
gcc.c-torture/compile/labels-3.c' .  What breaks, in which way?


Ciao,
Michael.

  reply	other threads:[~2011-04-07 12:35 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05  0:51 H.J. Lu
2011-04-05  6:44 ` Paolo Bonzini
2011-04-05 10:30   ` Richard Guenther
2011-04-06 17:03     ` H.J. Lu
2011-04-07  8:51       ` Richard Guenther
2011-04-07 12:35         ` Michael Matz [this message]
2011-04-07 14:05           ` H.J. Lu
2011-04-15 23:34             ` Steve Ellcey
2011-04-16  0:59               ` Michael Matz
2011-04-18 18:23                 ` Steve Ellcey
2011-04-18 21:27                   ` Richard Guenther

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=Pine.LNX.4.64.1104071423080.1989@wotan.suse.de \
    --to=matz@suse.de \
    --cc=bonzini@gnu.org \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=hjl.tools@gmail.com \
    --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).