public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "krischik at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/19851] New: The new GNAT can't compile PolyORB
Date: Wed, 09 Feb 2005 19:24:00 -0000	[thread overview]
Message-ID: <20050209130949.19851.krischik@users.sourceforge.net> (raw)

Hello,

when compiling PolyORB with the HEAD release I get a bug box:

+===========================GNAT BUG DETECTED==============================+
| 4.0.0 20050209 (experimental) (x86_64-unknown-linux-gnu) GCC error:      |
| in copy_tree_r, at tree-inline.c:2320                                    |
| Error detected at polyorb-binding_data-giop-diop.adb:131:8               |
| Please submit a bug report; see http://gcc.gnu.org/bugs.html.            |
| Include the entire contents of this bug box in the report.               |
| Include the exact gcc or gnatmake command that you entered.              |
| Also include sources listed below in gnatchop format                     |
| (concatenated together with no headers between files).                   |
+==========================================================================+

Please include these source files with error report
Note that list may not be accurate in some cases,
so please double check that the problem can still
be reproduced with the set of files listed.

If you ask me to I will attach all those files - but I guess you know where to 
get PolyORB from ;-).

I also made a little check on copy_tree_r and there is a new sanity check here:

  else if (TREE_CODE_CLASS (code) == tcc_type)
    *walk_subtrees = 0;
  else if (TREE_CODE_CLASS (code) == tcc_declaration)
    *walk_subtrees = 0;
  else if (TREE_CODE_CLASS (code) == tcc_constant)
    *walk_subtrees = 0;
  else
    gcc_assert (code != STATEMENT_LIST);

With Regards

Martin

-- 
           Summary: The new GNAT can't compile PolyORB
           Product: gcc
           Version: 4.0.0
            Status: UNCONFIRMED
          Severity: critical
          Priority: P2
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: krischik at users dot sourceforge dot net
                CC: gcc-bugs at gcc dot gnu dot org
 GCC build triplet: x86_64-unknown-linux-gnu
  GCC host triplet: x86_64-unknown-linux-gnu
GCC target triplet: x86_64-unknown-linux-gnu


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


             reply	other threads:[~2005-02-09 13:09 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-09 19:24 krischik at users dot sourceforge dot net [this message]
2005-02-09 19:25 ` [Bug ada/19851] " krischik at users dot sourceforge dot net
2005-02-09 20:58 ` charlet at gcc dot gnu dot org
2005-02-10 15:40 ` krischik at users dot sourceforge dot net
2005-02-10 15:55 ` krischik at users dot sourceforge dot net
2005-02-10 17:12 ` krischik at users dot sourceforge dot net
2005-02-15  1:00 ` laurent at guerby dot net

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=20050209130949.19851.krischik@users.sourceforge.net \
    --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).