[Bug ada/53684] New: Cannot raise custom exceptions in configurable runtime mode

[Bug ada/53684] New: Cannot raise custom exceptions in configurable runtime mode

[laguest at archeia dot com]

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

             Bug #: 53684
           Summary: Cannot raise custom exceptions in configurable runtime
                    mode
    Classification: Unclassified
           Product: gcc
           Version: 4.6.3
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: ada
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: laguest@archeia.com


According to the HIE docs,
(http://docs.adacore.com/gnat-hie-docs/html/gnathie_ug_3.html#SEC8) it states
when using a configurable runtime, exceptions declarations are valid.

In an attempt to build a hello world kernel for i386 using FS GNAT 4.6 on
Debian testing, it fails to build.

Compile the test with:

gnatmake -gnat2005 -g -a -x -gnatg -gnatec=./gnat.adc test.adb --RTS=. -cargs
-m32 -march=i386

Results are:

test.adb:5:04: construct not allowed in configurable run-time mode
test.adb:5:04: file a-except.ads not found
test.adb:5:04: entity "Ada.Exceptions.Raise_Exception" not available
gnatmake: "test.adb" compilation error

Expected results:

What is expected is that a-except is not looked for and the exception is caught
using the local handler or redirected to last_chance_handler.

Has been tested with GNAT GPL 2011, same results. Asked a friend with access to
GNAT PRO 7.1, same results again.

My System:

$ uname -a
Linux rogue 3.2.0-2-amd64 #1 SMP Mon May 21 17:45:41 UTC 2012 x86_64 GNU/Linux

$ gnat
GNAT 4.6
Copyright 1996-2010, Free Software Foundation, Inc.

List of available commands

gnat bind               gnatbind
gnat chop               gnatchop
gnat clean              gnatclean
gnat compile            gnatmake -f -u -c
gnat check              gnatcheck
gnat elim               gnatelim
gnat find               gnatfind
gnat krunch             gnatkr
gnat link               gnatlink
gnat list               gnatls
gnat make               gnatmake
gnat metric             gnatmetric
gnat name               gnatname
gnat preprocess         gnatprep
gnat pretty             gnatpp
gnat stack              gnatstack
gnat stub               gnatstub
gnat xref               gnatxref

All commands except chop, krunch and preprocess accept project file switches
-vPx, -Pprj and -Xnam=val

[Bug ada/53684] Cannot raise custom exceptions in configurable runtime mode

[ebotcazou at gcc dot gnu.org]

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

Eric Botcazou <ebotcazou at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
                 CC|                            |ebotcazou at gcc dot
                   |                            |gnu.org
         Resolution|                            |INVALID

--- Comment #1 from Eric Botcazou <ebotcazou at gcc dot gnu.org> 2012-06-17 08:03:13 UTC ---
> According to the HIE docs,
> (http://docs.adacore.com/gnat-hie-docs/html/gnathie_ug_3.html#SEC8) it states
> when using a configurable runtime, exceptions declarations are valid.

Note that this documentation isn't for the FSF compiler, so there is no point
in mentioning it here.

> In an attempt to build a hello world kernel for i386 using FS GNAT 4.6 on
> Debian testing, it fails to build.
> 
> Compile the test with:
> 
> gnatmake -gnat2005 -g -a -x -gnatg -gnatec=./gnat.adc test.adb --RTS=. -cargs
> -m32 -march=i386
> 
> Results are:
> 
> test.adb:5:04: construct not allowed in configurable run-time mode
> test.adb:5:04: file a-except.ads not found
> test.adb:5:04: entity "Ada.Exceptions.Raise_Exception" not available
> gnatmake: "test.adb" compilation error
> 
> Expected results:
> 
> What is expected is that a-except is not looked for and the exception is
> caught using the local handler or redirected to last_chance_handler.

No, you need to provide a specialized version of the package.