public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c/45079] [4.5 Regression] function names in error message (�c_maybe_const_expr� not supported by 'pp_c_expression') Date: Tue, 27 Jul 2010 15:50:00 -0000 [thread overview] Message-ID: <20100727155016.15979.qmail@sourceware.org> (raw) In-Reply-To: <bug-45079-11764@http.gcc.gnu.org/bugzilla/> [-- Warning: decoded text below may be mangled, UTF-8 assumed --] [-- Attachment #1: Type: text/plain, Size: 917 bytes --] ------- Comment #3 from jakub at gcc dot gnu dot org 2010-07-27 15:50 ------- Fixed on the trunk so far, with 4.5 will wait until 4.5.1 is released. -- jakub at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Known to fail|4.5.0 4.6.0 |4.5.0 Known to work|4.4.4 |4.4.4 4.6.0 Summary|[4.5/4.6 Regression] |[4.5 Regression] function |function names in error |names in error message |message |(�c_maybe_const_expr� |(�c_maybe_const_expr� |not supported by |not supported by |'pp_c_expression') |'pp_c_expression') | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45079
next prev parent reply other threads:[~2010-07-27 15:50 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-07-26 14:15 [Bug c/45079] New: function names in error message (�c_maybe_const_expr� " doko at ubuntu dot com 2010-07-26 14:47 ` [Bug c/45079] " jakub at gcc dot gnu dot org 2010-07-27 6:50 ` [Bug c/45079] [4.5/4.6 Regression] " pinskia at gcc dot gnu dot org 2010-07-27 15:47 ` jakub at gcc dot gnu dot org 2010-07-27 15:50 ` jakub at gcc dot gnu dot org [this message] 2010-07-31 9:35 ` [Bug c/45079] [4.5 " rguenth at gcc dot gnu dot org 2010-08-30 15:52 ` rguenth at gcc dot gnu dot org 2010-08-30 19:32 ` jakub at gcc dot gnu dot org 2010-08-30 19:34 ` jakub 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=20100727155016.15979.qmail@sourceware.org \ --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).