public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "richard-gccbugzilla at metafoo dot co.uk" <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 21:03:03 +0000 [thread overview] Message-ID: <bug-91292-4-RBOSCmA1qH@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 --- Comment #7 from Richard Smith <richard-gccbugzilla at metafoo dot co.uk> --- (In reply to Patrick Palka from comment #3) > 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", There is no such thing as a negative integer literal. The ABI document says "negative integer *values* are preceded with "n""; this case is reached when mangling fully-resolved template arguments via the <template-arg> ::= <expr-primary> production, not when mangling an instantiation-dependent expression. For example, given template<int> struct X {}; template<int N> void f(X<N * -1>, X<-1>) {} template void f<1>(X<-1>, X<-1>); the proper mangling is _Z1fILi1EEv1XIXmlT_ngLi1EEES0_ILin1EE using ngLi1E for the instantiation-dependent expression -1 and Lin1E for the non-instantiation-dependent value -1. (In reply to Patrick Palka from comment #4) > And if -(1) is to be mangled the same as -1, then shouldn't > > template<typename T> > typename std::enable_if<(int)sizeof(T) >= -(1), int>::type size1(T *t); > > template<typename T> > typename std::enable_if<(int)sizeof(T) >= -1, int>::type size1(T *t); > > be considered two declarations of the same function? But IIUC that would > contradict [temp.over.link]p5, which says > > Two expressions involving template parameters are considered equivalent if > two function definitions containing the expressions would satisfy the > one-definition rule > > but IIUC the one-definition rule fails here because -1 is not the same > (token-wise) as -(1). These declarations are functionally-equivalent but not equivalent, so a program is not permitted to contain both. That language rule exists in order to allow implementations to do things like ignore parentheses in mangling, as the Itanium C++ ABI does. Note that parentheses are never mangled (except for a weird corner case involving pointers to members), so if your argument were correct it would apply very broadly. For example, that argument would imply that -1 and (-1) would need different manglings.
next prev parent reply other threads:[~2021-09-24 21:03 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 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 [this message] 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-RBOSCmA1qH@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).