public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jason at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/44282] fastcall is not mangled at all
Date: Wed, 03 Jun 2015 21:10:00 -0000	[thread overview]
Message-ID: <bug-44282-4-CAmWfRi8E2@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-44282-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #9 from Jason Merrill <jason at gcc dot gnu.org> ---
Author: jason
Date: Wed Jun  3 21:09:25 2015
New Revision: 224101

URL: https://gcc.gnu.org/viewcvs?rev=224101&root=gcc&view=rev
Log:
        PR c++/44282
        * mangle.c (mangle_decl): Always SET_IDENTIFIER_GLOBAL_VALUE.
        (write_CV_qualifiers_for_type): Set G.need_abi_warning.
        (decl_implicit_alias_p): Split out from maybe_remove_implicit_alias.
        * cp-tree.h (DECL_REALLY_EXTERN): Handle null DECL_LANG_SPECIFIC.

Modified:
    trunk/gcc/cp/ChangeLog
    trunk/gcc/cp/cp-tree.h
    trunk/gcc/cp/mangle.c
    trunk/gcc/testsuite/g++.dg/abi/mangle-regparm.C
    trunk/gcc/testsuite/g++.dg/abi/mangle58.C


  parent reply	other threads:[~2015-06-03 21:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-44282-4@http.gcc.gnu.org/bugzilla/>
2013-01-05 16:14 ` harald at gigawatt dot nl
2013-11-17  7:57 ` pinskia at gcc dot gnu.org
2015-04-28 19:48 ` jason at gcc dot gnu.org
2015-06-02  2:29 ` jason at gcc dot gnu.org
2015-06-03 21:10 ` jason at gcc dot gnu.org [this message]
2015-09-14 19:55 ` jason at gcc dot gnu.org
2021-07-23  1:38 ` pinskia at gcc dot gnu.org
2021-07-27  2:20 ` pinskia at gcc dot gnu.org
2010-05-26 12:59 [Bug c++/44282] New: GCC allows for function overloading with pointer to function as parameter based on calling convention but assembler complains vadim dot atlygin at gmail dot com
2010-07-24 23:17 ` [Bug c++/44282] fastcall is not mangled at all pinskia at gcc dot gnu dot 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-44282-4-CAmWfRi8E2@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).