From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM autolearn=unavailable autolearn_force=no version=3.4.4 X-Received: by 10.66.159.103 with SMTP id xb7mr8748468pab.24.1466864862427; Sat, 25 Jun 2016 07:27:42 -0700 (PDT) X-Received: by 10.157.60.49 with SMTP id q46mr466127otc.0.1466864862362; Sat, 25 Jun 2016 07:27:42 -0700 (PDT) Path: eternal-september.org!reader01.eternal-september.org!reader02.eternal-september.org!news.eternal-september.org!mx02.eternal-september.org!feeder.eternal-september.org!news.glorb.com!r1no1823647ige.0!news-out.google.com!i62ni3703ith.0!nntp.google.com!r1no1823643ige.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: comp.lang.ada Date: Sat, 25 Jun 2016 07:27:42 -0700 (PDT) In-Reply-To: Complaints-To: groups-abuse@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=99.251.235.81; posting-account=qa2LvwoAAADwbTxJVBI5rHWSlh3aClXp NNTP-Posting-Host: 99.251.235.81 References: <35e9e475-7ddd-49ec-a7a3-1e72810b27f1@googlegroups.com> <9129d5b1-0363-4da7-9af2-8406e74b2d32@googlegroups.com> <24ed2937-9413-4948-aee7-e9bbd44a012c@googlegroups.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: Subject: Re: GNAT bug with protected procedure interrupt handler From: Daniel King Injection-Date: Sat, 25 Jun 2016 14:27:42 +0000 Content-Type: text/plain; charset=UTF-8 Xref: news.eternal-september.org comp.lang.ada:30933 Date: 2016-06-25T07:27:42-07:00 List-Id: On Saturday, 25 June 2016 10:15:12 UTC-3, Simon Wright wrote: > Daniel King writes: > > > On Saturday, 25 June 2016 04:28:01 UTC-3, Simon Wright wrote: > >> Egil H H writes: > >> > >> > On Saturday, June 25, 2016 at 4:40:31 AM UTC+2, Daniel King wrote: > >> >> > >> >> Has anyone else seen this problem, or are able to reproduce it? Have > >> >> you found a workaround? > >> >> > >> > > >> > Your code works here (except that RTC_Interrupt does not exist, so I > >> > changed it to RCC_Interrupt) > >> > >> Likewise. > >> > >> Compiling with -gnatG (shows a representation of the intermediate code) > >> sometimes shows up a problem. > > > > Thanks, whilst trying your suggestion I realised that actually, the > > code *compiles* fine for me too, the failure seems to occur only when > > using -gnatc to check syntax/semantics only. When I first posted I had > > not yet compiled the code because I was checking my .ads file since I > > had not yet written a corresponding .adb file to compile. > > > > So although the GNAT bug still occurs when using -gnatc at least the > > code compiles fine so I can still continue with my project. > > You appear to have come across another instance of PR66162! Yours is an > instance of comment 4. > > I still don't know what the language restrictions for building the > runtime are; I think that they relate to RTS units that the compiler > relies on to generate calls into the RTS, for instance for POs. So far, > off the top of my head, I have > > * no private withs > * no 'use' clauses in the spec > * no visibility of non-System, non-Interface packages > * no package aspects (not sure about this) > > [1] https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66162 Thanks for that, Simon. When I get some time I will look into the runtime to see if I can find any restriction violations. Did you ever find a write-up of the runtime language restrictions?