public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "sje at cup dot hp dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/28176] FAIL: gfortran.dg/actual_array_constructor_1.f90  -O0  (ICE)
Date: Wed, 18 Oct 2006 20:49:00 -0000	[thread overview]
Message-ID: <20061018204948.17211.qmail@sourceware.org> (raw)
In-Reply-To: <bug-28176-276@http.gcc.gnu.org/bugzilla/>



------- Comment #6 from sje at cup dot hp dot com  2006-10-18 20:49 -------
Well, I have tracked it back a little ways.  gfc_trans_vla_type_sizes_1 calls
gfc_trans_vla_one_sizepos with:

gfc_trans_vla_one_sizepos (&TYPE_SIZE (type), body);

If I print out type->type.size I see:

gdb) p debug_tree(type->type.size)
 <save_expr 800003ffbfe3d2c0
    type <integer_type 800003ffbfdaa160 bit_size_type public unsigned sizetype
T
I
        size <integer_cst 800003ffbfd9fdb0 constant invariant 128>
        unit size <integer_cst 800003ffbfd9fde0 constant invariant 16>
        align 128 symtab 0 alias set -1 precision 68 min <integer_cst
800003ffbf
db8000 0> max <integer_cst 800003ffbfd9ff00 0xfffffffffffffffff>>
    side-effects invariant

So I have a TImode here.  How it got here, I don't yet know.


-- 

sje at cup dot hp dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2006-10-18 20:49:47
               date|                            |


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


  parent reply	other threads:[~2006-10-18 20:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-27  1:47 [Bug fortran/28176] New: " danglin at gcc dot gnu dot org
2006-06-27  2:44 ` [Bug fortran/28176] " danglin at gcc dot gnu dot org
2006-06-28 14:32 ` pault at gcc dot gnu dot org
2006-07-06 16:49 ` danglin at gcc dot gnu dot org
2006-10-18 18:16 ` sje at cup dot hp dot com
2006-10-18 18:51 ` dave at hiauly1 dot hia dot nrc dot ca
2006-10-18 20:49 ` sje at cup dot hp dot com [this message]
2006-10-19  1:56 ` dave at hiauly1 dot hia dot nrc dot ca
2006-10-19 18:09 ` sje at cup dot hp dot com
2006-10-22 16:18 ` [Bug middle-end/28176] " dave at hiauly1 dot hia dot nrc dot ca
2006-11-18 23:17 ` danglin at gcc dot gnu dot org
2006-11-19  0:44 ` danglin at gcc dot gnu dot org
2006-11-19  0:50 ` danglin at gcc dot gnu dot org
2006-12-01  2:06 ` chaoyingfu 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=20061018204948.17211.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).