From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 98856] DIRT: Showdown broken graphics with Mesa built with -Ofast
Date: Sun, 05 Mar 2017 18:52:16 +0000 [thread overview]
Message-ID: <bug-98856-502-Uxp0i502qp@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-98856-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 501 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=98856
--- Comment #8 from Gregor Münch <gr.muench@gmail.com> ---
Created attachment 130076
--> https://bugs.freedesktop.org/attachment.cgi?id=130076&action=edit
garbled graphics #1
Found the problem. Seems like using -Ofast wasnt a good idea. Using -03
everything works as it should.
Still attaching screenshot showing the problem in case it is useful to others.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 1431 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-03-05 18:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-25 17:17 [Bug 98856] Dirt: Showdown broken graphics bugzilla-daemon
2017-01-05 13:46 ` bugzilla-daemon
2017-01-09 20:53 ` [Bug 98856] [Regression, SI] DIRT: " bugzilla-daemon
2017-01-09 21:08 ` bugzilla-daemon
2017-01-10 9:21 ` bugzilla-daemon
2017-01-11 9:15 ` bugzilla-daemon
2017-01-11 9:26 ` bugzilla-daemon
2017-01-23 9:21 ` bugzilla-daemon
2017-02-07 10:34 ` bugzilla-daemon
2017-03-05 18:40 ` [Bug 98856] DIRT: Showdown broken graphics with Mesa built with -Ofast bugzilla-daemon
2017-03-05 18:52 ` bugzilla-daemon [this message]
2017-03-22 16:57 ` bugzilla-daemon
2018-01-21 19:21 ` bugzilla-daemon
2018-03-08 0:42 ` 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-98856-502-Uxp0i502qp@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.