dri-devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 92214] Flightgear crashes during splashboot with R600 driver and mesa 11.0.2
Date: Wed, 07 Oct 2015 13:28:59 +0000	[thread overview]
Message-ID: <bug-92214-502-oECIFf1WN5@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-92214-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 856 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=92214

--- Comment #14 from Barto <mister.freeman@laposte.net> ---
(In reply to Roland Scheidegger from comment #13)
> Does not necessarily mean it is a bug in llvm, maybe we're initializing it
> wrong or something (there were some recent patches to fix some threading
> issues in gallivm recently). Not my area of expertise, though...

I tried the git version of mesa ( master branch ) --> same crash with llvm 3.7

what I am sure is that there is no problem with llvm 3.6.2 and mesa 11.x ( and
even mesa 10.6 + llvm 3.6.2 )

here is the release note of llvm 3.7 :

http://llvm.org/releases/3.7.0/docs/ReleaseNotes.html

I still have no answer from llvm website about my bugreport,

I will try to find the faulty commit in llvm 3.7.x

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 1810 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

  parent reply	other threads:[~2015-10-07 13:28 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-01 17:17 [Bug 92214] Flightgear crashes during splashboot with R600 driver and mesa 11.0.2 bugzilla-daemon
2015-10-01 17:18 ` bugzilla-daemon
2015-10-01 17:25 ` bugzilla-daemon
2015-10-01 17:34 ` bugzilla-daemon
2015-10-01 17:48 ` bugzilla-daemon
2015-10-01 17:54 ` bugzilla-daemon
2015-10-01 18:40 ` bugzilla-daemon
2015-10-01 19:48 ` bugzilla-daemon
2015-10-01 20:02 ` bugzilla-daemon
2015-10-01 21:36 ` bugzilla-daemon
2015-10-02  1:03 ` bugzilla-daemon
2015-10-02  2:29 ` bugzilla-daemon
2015-10-02  2:55 ` bugzilla-daemon
2015-10-02  3:37 ` bugzilla-daemon
2015-10-07 13:28 ` bugzilla-daemon [this message]
2015-10-08 16:08 ` [Bug 92214] Flightgear crashes during splashboot with R600 driver, LLVM 3.7.0 " bugzilla-daemon
2015-10-09 16:44 ` bugzilla-daemon
2015-10-09 16:45 ` bugzilla-daemon
2015-10-09 16:47 ` bugzilla-daemon
2015-10-09 17:16 ` bugzilla-daemon
2015-10-09 18:34 ` bugzilla-daemon
2015-10-09 18:43 ` bugzilla-daemon
2015-10-09 18:53 ` bugzilla-daemon
2015-10-09 19:17 ` bugzilla-daemon
2015-10-11 14:38 ` bugzilla-daemon
2015-10-11 16:15 ` bugzilla-daemon
2015-10-12 11:42 ` bugzilla-daemon
2015-10-12 16:54 ` bugzilla-daemon
2015-10-12 21:14 ` bugzilla-daemon
2015-10-13  2:07 ` bugzilla-daemon
2015-10-13  7:06 ` bugzilla-daemon
2015-10-14  6:36 ` bugzilla-daemon
2015-10-22  1:49 ` bugzilla-daemon
2015-10-22  3:14 ` bugzilla-daemon
2015-10-22 19:41 ` bugzilla-daemon
2015-10-22 21:54 ` bugzilla-daemon
2015-10-22 21:59 ` bugzilla-daemon
2015-10-22 22:36 ` bugzilla-daemon
2015-10-23 10:37 ` bugzilla-daemon
2015-10-23 10:39 ` bugzilla-daemon
2015-10-23 13:55 ` bugzilla-daemon
2015-10-23 19:26 ` 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-92214-502-oECIFf1WN5@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