public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "mueller at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/36453] New: PR36320 breaks boost Date: Fri, 06 Jun 2008 17:54:00 -0000 [thread overview] Message-ID: <bug-36453-12049@http.gcc.gnu.org/bugzilla/> (raw) testcase: === Cut === #if !defined(BOOST_PP_IS_ITERATING) #elif BOOST_PP_ITERATION_DEPTH() == 1 #endif === Cut === error: missing binary operator before token "(" from reading the PR36320, this behaviour doesn't seem to be intended. It was intended to only add a check for non-null argument. -- Summary: PR36320 breaks boost Product: gcc Version: 4.4.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: preprocessor AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: mueller at gcc dot gnu dot org http://gcc.gnu.org/bugzilla/show_bug.cgi?id=36453
next reply other threads:[~2008-06-06 17:54 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-06-06 17:54 mueller at gcc dot gnu dot org [this message] 2008-06-06 20:04 ` [Bug preprocessor/36453] " rguenth at gcc dot gnu dot org 2008-06-06 20:24 ` tromey at gcc dot gnu dot org 2008-06-10 22:15 ` mueller at gcc dot gnu dot org 2008-07-06 3:26 ` tromey at gcc dot gnu dot org 2008-07-07 9:26 ` mueller at gcc dot gnu dot org 2008-09-14 8:09 ` schwab at suse dot de 2008-10-09 14:47 ` schwab at suse dot de 2008-10-09 20:40 ` sam at gcc dot gnu dot org 2008-12-05 12:30 ` rguenth at gcc dot gnu dot org 2010-05-06 18:03 ` knocte at gmail dot com 2010-05-07 8:40 ` rguenther at suse dot de
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-36453-12049@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).