From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65438] GTK apps crash X11 since last update of LLVMM
Date: Thu, 06 Jun 2013 10:03:42 +0000 [thread overview]
Message-ID: <bug-65438-502-Vp7sj3SA3b@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-65438-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 470 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=65438
--- Comment #1 from Michel Dänzer <michel@daenzer.net> ---
I can't reproduce this. Make sure your LLVM and Mesa snapshots are both up to
date and built consistently.
If that doesn't help, can you isolate which LLVM change introduced the problem
for you? The Git mirror at http://llvm.org/git/llvm.git might be useful for
that.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1299 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2013-06-06 10:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-06 1:51 [Bug 65438] New: GTK apps crash X11 since last update of LLVMM bugzilla-daemon
2013-06-06 1:51 ` [Bug 65438] " bugzilla-daemon
2013-06-06 10:03 ` bugzilla-daemon [this message]
2013-06-06 15:13 ` bugzilla-daemon
2013-06-07 10:21 ` bugzilla-daemon
2013-06-08 13:01 ` bugzilla-daemon
2013-06-08 23:49 ` bugzilla-daemon
2013-06-08 23:52 ` bugzilla-daemon
2013-06-09 0:12 ` bugzilla-daemon
2013-06-09 14:53 ` bugzilla-daemon
2013-06-10 16:42 ` bugzilla-daemon
2013-06-10 20:19 ` bugzilla-daemon
2013-06-10 22:13 ` bugzilla-daemon
2013-06-14 8:28 ` bugzilla-daemon
2013-06-14 18:55 ` 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-65438-502-Vp7sj3SA3b@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).