public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rguenth at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/109492] gcc/fortran/trans-expr.cc:3407:17: error: call of overloaded ‘abs(long long int&)’ is ambiguous Date: Thu, 13 Apr 2023 11:37:34 +0000 [thread overview] Message-ID: <bug-109492-4-9ye78OF3sQ@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-109492-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=109492 Richard Biener <rguenth at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Ever confirmed|0 |1 Status|UNCONFIRMED |NEW Last reconfirmed| |2023-04-13 --- Comment #2 from Richard Biener <rguenth at gcc dot gnu.org> --- It should use abs_hwi () instead (or maybe absu_hwi for safety).
next prev parent reply other threads:[~2023-04-13 11:37 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-04-12 22:09 [Bug fortran/109492] New: " redi at gcc dot gnu.org 2023-04-12 22:13 ` [Bug fortran/109492] " redi at gcc dot gnu.org 2023-04-13 11:37 ` rguenth at gcc dot gnu.org [this message] 2023-04-13 19:03 ` anlauf at gcc dot gnu.org 2023-04-13 19:34 ` redi at gcc dot gnu.org 2023-04-13 20:47 ` cvs-commit at gcc dot gnu.org 2023-04-14 19:25 ` anlauf 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-109492-4-9ye78OF3sQ@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).