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: Mon, 14 Sep 2015 19:55:00 -0000 [thread overview] Message-ID: <bug-44282-4-0fMz1GOt2e@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 #10 from Jason Merrill <jason at gcc dot gnu.org> --- Author: jason Date: Mon Sep 14 19:54:27 2015 New Revision: 227761 URL: https://gcc.gnu.org/viewcvs?rev=227761&root=gcc&view=rev Log: PR c++/44282 * mangle.c (write_CV_qualifiers_for_type): Also warn about regparm mangling with lower -fabi-version. Added: trunk/gcc/testsuite/g++.dg/abi/mangle-regparm1a.C Modified: trunk/gcc/cp/ChangeLog trunk/gcc/cp/mangle.c
next prev parent reply other threads:[~2015-09-14 19:55 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 2015-09-14 19:55 ` jason at gcc dot gnu.org [this message] 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-0fMz1GOt2e@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).