public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "markus dot heichel at comsoft dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/29320]  New: Segfault and strange behaviour related to "use" clauses
Date: Mon, 02 Oct 2006 12:05:00 -0000	[thread overview]
Message-ID: <bug-29320-12295@http.gcc.gnu.org/bugzilla/> (raw)

GCC seems to have more problems with "use" clauses (see also bug #26529).

gcc: Internal error: Segmentation fault (program gnat1)

The compiler has been compiled from source by:
> configure --prefix=/opt/gcc-4.1.1 --enable-languages=ada,c
> make bootstrap
> make install

The problem can be reproduced by compiling the source file below, using the
following command line:

gcc -c command.ads

The solution of the problem in this case is to use the correct range 0..6 for
INFO_T.COMMAND_NAME, but gcc should have printed an error message instead of
crashing, shouldn't it?

The compiler does not crash when size 8 is used for COMMAND_KIND_T, but how are
the enum values represented in COMMAND_NAME in this case?

command.ads
=======================================================
package COMMAND is

   type COMMAND_KIND_T is (START, STOP);

   for COMMAND_KIND_T use (START => 80, STOP => 81);

   -- for COMMAND_KIND_T'size use 8; -- not crashing
   for COMMAND_KIND_T'size use 16;   -- crashing

   type SUB_COMMAND_KIND_T is new COMMAND_KIND_T range START..STOP;

   for SUB_COMMAND_KIND_T'size use 7;

   type INFO_T (COMMAND_NAME : SUB_COMMAND_KIND_T := START) is record
      case COMMAND_NAME is
         when others     => null;
      end case;
   end record;

   for INFO_T use record
      COMMAND_NAME       at 0 range 0..4;
   end record;

end COMMAND;
=======================================================


-- 
           Summary: Segfault and strange behaviour related to "use" clauses
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: markus dot heichel at comsoft dot de
 GCC build triplet: i686-pc-linux
  GCC host triplet: i686-pc-linux
GCC target triplet: i686-pc-linux


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


             reply	other threads:[~2006-10-02 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-02 12:05 markus dot heichel at comsoft dot de [this message]
2006-10-04 17:56 ` [Bug ada/29320] [Ada] gnat1 segfault related to "use" representation clauses laurent at guerby dot net
2008-04-12 16:25 ` sam 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=bug-29320-12295@http.gcc.gnu.org/bugzilla/ \
    --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).