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=0.4 required=5.0 tests=BAYES_00,FORGED_MUA_MOZILLA autolearn=no autolearn_force=no version=3.4.4 X-Google-Thread: 103376,53dee61641b15f6c X-Google-NewGroupId: yes X-Google-Attributes: gida07f3367d7,domainid0,public,usenet X-Google-Language: ENGLISH,ASCII-7-bit Received: by 10.68.220.230 with SMTP id pz6mr868224pbc.3.1340311864925; Thu, 21 Jun 2012 13:51:04 -0700 (PDT) Path: l9ni4448pbj.0!nntp.google.com!news1.google.com!npeer02.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!nntp.club.cc.cmu.edu!feeder.erje.net!news2.arglkargh.de!news.musoftware.de!wum.musoftware.de!de-l.enfer-du-nord.net!feeder2.enfer-du-nord.net!usenet-fr.net!feeder1-2.proxad.net!proxad.net!feeder2-2.proxad.net!newsfeed.arcor.de!newsspool4.arcor-online.net!news.arcor.de.POSTED!not-for-mail Date: Thu, 21 Jun 2012 22:51:05 +0200 From: Georg Bauhaus User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 MIME-Version: 1.0 Newsgroups: comp.lang.ada Subject: Re: Bug or feature: representation makes aliasing with renaming declaration an error References: <4fe22876$0$9510$9b4e6d93@newsspool1.arcor-online.net> In-Reply-To: Message-ID: <4fe38938$0$9526$9b4e6d93@newsspool1.arcor-online.net> Organization: Arcor NNTP-Posting-Date: 21 Jun 2012 22:51:04 CEST NNTP-Posting-Host: bdad2d22.newsspool1.arcor-online.net X-Trace: DXC=@9GR[BOIa\:LNKYb?b>076ic==]BZ:af>4Fo<]lROoR1nkgeX?EC@@0f=EcIUW:@h2PCY\c7>ejV8I>7g]FTgDD93>X8Fic=lm: X-Complaints-To: usenet-abuse@arcor.de X-Received-Bytes: 1729 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Date: 2012-06-21T22:51:04+02:00 List-Id: On 20.06.12 22:45, Adam Beneschan wrote: >> 12. X : Ptr := Nm'Access; >> | >> >>> prefix of "Access" attribute must be aliased >> >> The error goes away when line 4 is commented. >> Is this expected behavior or is my compiler confused? > > This appears to be a compiler bug. Thank you for your judgement, this is reassuring. FTR, bug report #53747 now addresses this for GCC 4.8.0.