public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gj at pointblue dot com dot pl" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/18968] [4.0 regression] ICE: tree check: expected ssa_name, have addr_expr in vrp_hash
Date: Thu, 17 Feb 2005 17:05:00 -0000	[thread overview]
Message-ID: <20050217132618.21328.qmail@sourceware.org> (raw)
In-Reply-To: <20041213212814.18968.schwab@suse.de>


------- Additional Comments From gj at pointblue dot com dot pl  2005-02-17 13:26 -------
Fixed for that specific testcase, but can't compile kernel today. 
Kernel version 2.6.11-rc4 vanilia, 
gcc (GCC) 4.0.0 20050217 (experimental) 
 
  CC      arch/x86_64/kernel/setup.o 
arch/x86_64/kernel/setup.c: In function 'setup_arch': 
arch/x86_64/kernel/setup.c:453: internal compiler error: tree check: expected 
ssa_name, have addr_expr in vrp_hash, at tree-ssa-dom.c:3310 
Please submit a full bug report, 
with preprocessed source if appropriate. 
See <URL:http://gcc.gnu.org/bugs.html> for instructions. 
make[1]: *** [arch/x86_64/kernel/setup.o] Error 1 
make: *** [arch/x86_64/kernel] Error 2 
 
.... 
#define EBDA_ADDR_POINTER 0x40E 
static void __init reserve_ebda_region(void) 
{ <-here 
        unsigned int addr; 
        /** 
         * there is a real-mode segmented pointer pointing to the 
         * 4K EBDA area at 0x40E 
         */ 
..... 
 

-- 


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


  parent reply	other threads:[~2005-02-17 13:26 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 21:28 [Bug middle-end/18968] New: " schwab at suse dot de
2004-12-13 21:30 ` [Bug middle-end/18968] " schwab at suse dot de
2004-12-13 21:30 ` [Bug tree-optimization/18968] " pinskia at gcc dot gnu dot org
2004-12-13 21:32 ` pinskia at gcc dot gnu dot org
2004-12-13 22:17 ` reichelt at gcc dot gnu dot org
2004-12-13 22:22 ` pinskia at gcc dot gnu dot org
2004-12-13 22:38 ` pinskia at gcc dot gnu dot org
2004-12-13 22:53 ` [Bug c++/18968] " pinskia at gcc dot gnu dot org
2004-12-13 22:54 ` reichelt at gcc dot gnu dot org
2004-12-13 23:00 ` law at redhat dot com
2004-12-13 23:18 ` pinskia at gcc dot gnu dot org
2004-12-13 23:50 ` pinskia at gcc dot gnu dot org
2004-12-14  0:38 ` law at redhat dot com
2004-12-14  0:42 ` law at redhat dot com
2004-12-14  2:22 ` cvs-commit at gcc dot gnu dot org
2004-12-14  2:22 ` pinskia at gcc dot gnu dot org
2005-02-17 17:05 ` gj at pointblue dot com dot pl [this message]
2005-02-17 17:48 ` pinskia at gcc dot gnu dot org
2005-02-17 17:57 ` gj at pointblue dot com dot pl

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=20050217132618.21328.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).