dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48305] llpp gets segfault in r600g_dri.so
Date: Thu, 05 Apr 2012 06:48:04 +0000	[thread overview]
Message-ID: <bug-48305-502-IaYGg3PLl4@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-48305-502@http.bugs.freedesktop.org/>

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

--- Comment #6 from Michel Dänzer <michel@daenzer.net> 2012-04-05 06:48:04 UTC ---
(In reply to comment #5)
> After playing with compilation flags to get meaningful backtrace I found that
> this segfault happens only with -O3… Dunno if this is considered as a bug.

It's a bug *somewhere*, but it looks like it could be in the compiler... Maybe
you can try isolating which specific option implied by -O3 but not by -O2 makes
the difference.

-- 
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2012-04-05 13:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-04 17:33 [Bug 48305] New: llpp gets segfault in r600g_dri.so bugzilla-daemon
2012-04-04 13:40 ` [Bug 48305] " bugzilla-daemon
2012-04-04 18:06 ` bugzilla-daemon
2012-04-04 20:42 ` bugzilla-daemon
2012-04-04 20:45 ` bugzilla-daemon
2012-04-05  6:48 ` bugzilla-daemon [this message]
2012-04-05 12:54 ` bugzilla-daemon
2012-04-06  0:49 ` bugzilla-daemon
2012-04-06 11:11 ` bugzilla-daemon
2012-04-07 14:28 ` bugzilla-daemon
2019-09-18 18:59 ` 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-48305-502-IaYGg3PLl4@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).