public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug plugins/59335] Plugin doesn't build on trunk Date: Mon, 14 Apr 2014 10:02:00 -0000 [thread overview] Message-ID: <bug-59335-4-ML3cckqo5x@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-59335-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59335 --- Comment #23 from Jakub Jelinek <jakub at gcc dot gnu.org> --- Created attachment 32593 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=32593&action=edit gcc49-pr59335.patch So, let's add the headers added in 4.9 and other stuff shouldn't be a regression from 4.9 then and can be added on a case by case basis. For 5.0 I hope something smarter will be added and we'll have some better plugin API than everything is the API.
next prev parent reply other threads:[~2014-04-14 10:02 UTC|newest] Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-11-29 3:00 [Bug plugins/59335] New: " joey.ye at arm dot com 2013-11-29 3:34 ` [Bug plugins/59335] " pinskia at gcc dot gnu.org 2014-01-10 17:54 ` sje at gcc dot gnu.org 2014-01-10 17:56 ` sje at gcc dot gnu.org 2014-01-11 1:20 ` pageexec at gmail dot com 2014-01-11 13:01 ` ubizjak at gmail dot com 2014-01-26 23:34 ` pageexec at gmail dot com 2014-02-13 5:51 ` joey.ye at arm dot com 2014-02-13 11:31 ` pageexec at gmail dot com 2014-02-14 1:29 ` joey.ye at arm dot com 2014-02-18 15:02 ` pageexec at gmail dot com 2014-03-04 13:48 ` pageexec at gmail dot com 2014-03-05 9:52 ` jakub at gcc dot gnu.org 2014-03-05 15:07 ` jakub at gcc dot gnu.org 2014-03-05 21:29 ` jakub at gcc dot gnu.org 2014-03-05 22:47 ` pageexec at gmail dot com 2014-04-13 20:04 ` pageexec at gmail dot com 2014-04-13 20:46 ` ubizjak at gmail dot com 2014-04-14 7:48 ` jakub at gcc dot gnu.org 2014-04-14 9:43 ` jakub at gcc dot gnu.org 2014-04-14 9:49 ` pageexec at gmail dot com 2014-04-14 10:02 ` jakub at gcc dot gnu.org [this message] 2014-04-15 8:03 ` jakub at gcc dot gnu.org 2014-04-15 8:04 ` jakub at gcc dot gnu.org 2014-04-15 8:10 ` jakub at gcc dot gnu.org 2014-08-25 2:16 ` terry.guo at arm dot com 2014-08-25 2:17 ` joey.ye at arm dot com 2014-09-05 6:52 ` jye2 at gcc dot gnu.org 2014-09-05 6:56 ` joey.ye at arm dot com 2021-08-28 4:18 ` pinskia 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-59335-4-ML3cckqo5x@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).