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 c++/55742] [4.8 regression] __attribute__ in class function declaration cause "prototype does not match" errors. Date: Mon, 14 Jan 2013 14:38:00 -0000 [thread overview] Message-ID: <bug-55742-4-V1fuLNdEhF@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-55742-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55742 --- Comment #9 from Richard Biener <rguenth at gcc dot gnu.org> 2013-01-14 14:38:04 UTC --- I'd say once a target attribute appears at a declaration (non-definition) MV needs to be disabled. Or, the declarations target attribute and those at the MV definitions need to be merged. Thus, a declarations target attribute applies to all definitions (thus all MV variants).
next prev parent reply other threads:[~2013-01-14 14:38 UTC|newest] Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-12-19 16:46 [Bug c++/55742] New: " dnovillo at gcc dot gnu.org 2012-12-19 23:30 ` [Bug c++/55742] " tmsriram at google dot com 2012-12-20 18:00 ` dnovillo at gcc dot gnu.org 2012-12-20 18:21 ` tmsriram at google dot com 2012-12-20 18:24 ` dnovillo at google dot com 2012-12-20 19:37 ` tmsriram at google dot com 2012-12-20 19:52 ` xinliangli at gmail dot com 2013-01-10 22:10 ` tmsriram at google dot com 2013-01-14 14:33 ` [Bug c++/55742] [4.8 regression] " jason at gcc dot gnu.org 2013-01-14 14:35 ` rguenth at gcc dot gnu.org 2013-01-14 14:38 ` rguenth at gcc dot gnu.org [this message] 2013-01-14 15:14 ` jakub at gcc dot gnu.org 2013-01-14 17:17 ` xinliangli at gmail dot com 2013-01-14 17:21 ` xinliangli at gmail dot com 2013-01-14 17:46 ` tmsriram at google dot com 2013-01-14 17:50 ` xinliangli at gmail dot com 2013-01-14 18:07 ` tmsriram at google dot com 2013-01-14 18:26 ` jakub at gcc dot gnu.org 2013-01-14 18:33 ` jakub at gcc dot gnu.org 2013-01-14 20:18 ` xinliangli at gmail dot com 2013-01-14 20:24 ` jakub at gcc dot gnu.org 2013-01-14 20:30 ` xinliangli at gmail dot com 2013-01-15 18:45 ` jason at gcc dot gnu.org 2013-01-15 19:03 ` xinliangli at gmail dot com 2013-01-16 8:12 ` jakub at gcc dot gnu.org 2013-01-16 15:54 ` jason at gcc dot gnu.org 2013-01-16 16:03 ` jakub at gcc dot gnu.org 2013-01-16 16:06 ` richard.guenther at gmail dot com 2013-01-16 17:21 ` tmsriram at google dot com 2013-01-16 17:26 ` tmsriram at google dot com 2013-01-16 20:04 ` jason at gcc dot gnu.org 2013-01-17 22:45 ` xinliangli at gmail dot com 2013-01-18 9:49 ` richard.guenther at gmail dot com 2013-01-18 14:19 ` jakub at gcc dot gnu.org 2013-01-18 16:59 ` jason at gcc dot gnu.org 2013-01-18 17:28 ` xinliangli at gmail dot com 2013-01-18 17:52 ` jakub at gcc dot gnu.org 2013-01-18 18:03 ` tmsriram at google dot com 2013-01-18 18:08 ` tmsriram at google dot com 2013-01-18 19:53 ` tmsriram at google dot com 2013-01-19 10:14 ` jakub at gcc dot gnu.org 2013-01-19 10:28 ` jakub at gcc dot gnu.org 2013-01-19 17:18 ` tmsriram at google dot com 2013-01-21 11:41 ` jakub at gcc dot gnu.org 2013-01-23 16:39 ` jakub at gcc dot gnu.org 2013-01-30 18:05 ` jakub at gcc dot gnu.org 2013-01-30 18:18 ` jakub 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-55742-4-V1fuLNdEhF@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).