procedure renames creates a primitive operation?

[Jere <jhb.chat@gmail.com>]

I was curious if this was a bug or intended.  
Given the following code:

***************************************************

procedure Main is

   package Some_Package is

      type Main_Type is tagged null record;
      
      package Non_Primitive_Ops is
         procedure Some_Op(Obj : Main_Type) is null;
      end Non_Primitive_Ops;
      
      -- without this line, the file correctly generates compiler errors
      procedure Some_Op(Obj : Main_Type) renames Non_Primitive_Ops.Some_Op;

   end Some_Package;

   Var : Some_Package.Main_Type;
   
   package Other_Package is
      
      type Derived_Type is new Some_Package.Main_Type with null record;
      
      
      -- Should this create a compiler error?
      overriding
      procedure Some_Op(Obj : Derived_Type) is null;
      
   end Other_Package;
   
begin
   
   Var.Some_Op; -- Should this create a compiler error?

end Main;

***************************************************

I used a renames clause to bring a non primitive operation 
into scope (for client readability when calling the procedure).  
However, when I did that, it created a primitive operation.  
Is this correct behavior or a bug?

It seems odd that a procedure created through a renames clause 
would be primitive, but perhaps it is intended?