From: Simon Wright <simon@pushface.org>
Subject: Re: Interrupt_Handler and "directly specified"
Date: Fri, 20 Nov 2015 19:22:14 +0000
Date: 2015-11-20T19:22:14+00:00 [thread overview]
Message-ID: <lywptcfpcp.fsf@pushface.org> (raw)
In-Reply-To: n2nou4$jap$1@dont-email.me
"G.B." <bauhaus@futureapps.invalid> writes:
> For a protected handler, I had specified an aspect,
>
> procedure On_1
> with Interrupt_Handler => True;
>
> and got a strange compiler diagnostic, listed below.
> Compiling: parent-admin.adb
> Source file time stamp: 2015-11-20 18:18:17
> Compiled at: 2015-11-20 19:18:28
>
> 1.
> 2. package body Parent.Admin is
> 3.
> 4. protected body P1 is
> 5.
> 6. procedure On_1
> |
> >>> expected type "System.Interrupts.Dynamic_Interrupt_Protection"
> >>> found private type
> "System.Tasking.Protected_Objects.Protection"
>
> 7. is begin
> 8. null;
> 9. end On_1;
> 10.
> 11. end P1;
> 12.
> 13. end Parent.Admin;
> 13 lines: 2 errors
(a) I can only see one error?
(b) that is a compiler error (problem with internal representations of
intermediate code, I think)
(c) what is it doing on the body!!
(d) GCC 6 does the same
(e) if you say "with Interrupt_Handler => False" it compiles OK, but who
knows what it means!
Report the error!
next prev parent reply other threads:[~2015-11-20 19:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 18:33 Interrupt_Handler and "directly specified" G.B.
2015-11-20 19:22 ` Simon Wright [this message]
2015-11-20 21:25 ` Randy Brukardt
2015-11-22 9:59 ` Georg Bauhaus
replies disabled
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox