public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "p.p11 at orange dot fr" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug ada/113351] New: Primitive renaming, error: too many arguments in call. Date: Fri, 12 Jan 2024 10:40:55 +0000 [thread overview] Message-ID: <bug-113351-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=113351 Bug ID: 113351 Summary: Primitive renaming, error: too many arguments in call. Product: gcc Version: 13.2.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: ada Assignee: unassigned at gcc dot gnu.org Reporter: p.p11 at orange dot fr CC: dkm at gcc dot gnu.org Target Milestone: --- Created attachment 57050 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=57050&action=edit Reproducer. Let's define: package Loggings is type Logging is tagged record Output : Ada.Text_IO.File_Access; end record; procedure Log (Handler : Logging; Msg : String); procedure Log (Handler : Logging; Msg : String; Err : Natural); end Loggings; and declare: My_Handler : aliased Loggings.Logging := (Output => Ada.Text_IO.Current_Output); My_Generic_Handler : access Loggings.Logging'Class := My_Handler'Access; procedure My_Log_3 (Msg : String) renames My_Generic_Handler.Log; procedure My_Log_4 (Msg : String; Err : Natural) renames My_Generic_Handler.Log; -- error: too many arguments in call Result with GNAT 13.2.0: test_20240110_renproc.adb:48:14: error: too many arguments in call to "log" Expected result: No error for My_Log_4 renaming declaration as for My_Log_3. Discussion on CLA: https://groups.google.com/g/comp.lang.ada/c/wpjZmaqmLrk/m/of81pnmeAQAJ
next reply other threads:[~2024-01-12 10:40 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2024-01-12 10:40 p.p11 at orange dot fr [this message] 2024-01-19 11:34 ` [Bug ada/113351] error on primitive renaming: " ebotcazou at gcc dot gnu.org 2024-01-20 9:02 ` p.p11 at orange dot fr 2024-01-20 9:34 ` ebotcazou at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-113351-4@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).