public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ppalka at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/91292] Mangler incorrectly handles negative numbers in expressions
Date: Fri, 24 Sep 2021 15:55:51 +0000	[thread overview]
Message-ID: <bug-91292-4-AZs6InMCCH@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-91292-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=91292

Patrick Palka <ppalka at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ppalka at gcc dot gnu.org

--- Comment #3 from Patrick Palka <ppalka at gcc dot gnu.org> ---
> According to http://itanium-cxx-abi.github.io/cxx-abi/abi.html#expressions , a negative number isn't treated as a negative literal; it is a negated number.  This means that it is mangled as though it were positive, and then its negation is mangled.  So -1 and -(1) are treated the same.

Hmm, but according to
http://itanium-cxx-abi.github.io/cxx-abi/abi.html#mangling.literal the mangling
of a negative integer literal is prefixed with "n", and according to
http://itanium-cxx-abi.github.io/cxx-abi/abi.html#mangle.operator-name the
mangling of -<expr> is prefixed with "ng".  So I don't see why -1 and -(1)
should be given the same mangling.  ISTM GCC is already getting the mangling
right.

       reply	other threads:[~2021-09-24 15:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-91292-4@http.gcc.gnu.org/bugzilla/>
2021-09-24 15:55 ` ppalka at gcc dot gnu.org [this message]
2021-09-24 16:11 ` ppalka at gcc dot gnu.org
2021-09-24 16:13 ` ppalka at gcc dot gnu.org
2021-09-24 16:36 ` cvs-commit at gcc dot gnu.org
2021-09-24 21:03 ` richard-gccbugzilla at metafoo dot co.uk
2021-09-27 13:50 ` ppalka at gcc dot gnu.org
2021-10-06 14:15 ` cvs-commit 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-91292-4-AZs6InMCCH@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: link
Be 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).