From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 49110] debug build: AMDILCFGStructurizer.cpp:1751:3: error: 'isCurrentDebugType' was not declared in this scope
Date: Mon, 07 May 2012 23:50:36 +0000 [thread overview]
Message-ID: <bug-49110-502-euHjuL3dDR@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-49110-502@http.bugs.freedesktop.org/>
https://bugs.freedesktop.org/show_bug.cgi?id=49110
--- Comment #5 from Mike Mestnik <cheako+bugs_freedesktop_org@mikemestnik.net> 2012-05-07 16:50:36 PDT ---
Commit c425c3823fbd475dc83211fef47f7ea58421ed17 should have fixed this, but it
don't. I've looked at the llvm headers and it looks like a number of
preprocessor macros will include these, if NDEBUG is not set.
I'm now going to try and set that.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
next prev parent reply other threads:[~2012-05-07 23:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 14:03 [Bug 49110] New: AMDILCFGStructurizer.cpp:1751:3: error: 'isCurrentDebugType' was not declared in this scope bugzilla-daemon
2012-04-24 23:04 ` [Bug 49110] " bugzilla-daemon
2012-04-26 13:14 ` bugzilla-daemon
2012-05-04 21:07 ` bugzilla-daemon
2012-05-07 3:36 ` bugzilla-daemon
2012-05-07 3:38 ` [Bug 49110] debug build: " bugzilla-daemon
2012-05-07 3:39 ` bugzilla-daemon
2012-05-07 3:40 ` bugzilla-daemon
2012-05-07 3:43 ` bugzilla-daemon
2012-05-07 3:44 ` bugzilla-daemon
2012-05-07 23:50 ` bugzilla-daemon [this message]
2012-05-08 1:31 ` bugzilla-daemon
2012-05-09 3:25 ` bugzilla-daemon
2012-05-10 21:43 ` bugzilla-daemon
2012-09-01 19:09 ` bugzilla-daemon
2012-09-02 15:45 ` bugzilla-daemon
2012-09-02 19:23 ` bugzilla-daemon
2012-09-02 20:52 ` bugzilla-daemon
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-49110-502-euHjuL3dDR@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.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: link
Be 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 NNTP newsgroup(s).