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 101484] [regression, bisected] Steam fails to render content, if mesa is compiled with -O2 -march=haswell
Date: Wed, 26 Jul 2017 19:30:35 +0000	[thread overview]
Message-ID: <bug-101484-502-FD6fIxXR8e@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-101484-502@http.bugs.freedesktop.org/>


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

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

--- Comment #14 from LoneVVolf <lonewolf@xs4all.nl> ---
(In reply to Gregor Münch from comment #5)
> Ive tested this now, and again its a compiler flags issue.
> Arch standard clfags are:
> CFLAGS="-march=native -O2 -pipe -fstack-protector-strong"
> 

for clarity, default on archlinux is NOT -march=native .

The current pacman version is 5.0.2-2 and it has these defaults :

# ARCHITECTURE, COMPILE FLAGS
#########################################################################
#
CARCH="x86_64"
CHOST="x86_64-pc-linux-gnu"

#-- Compiler and Linker Flags
# -march (or -mcpu) builds exclusively for an architecture
# -mtune optimizes for an architecture, but builds for whole processor family
CPPFLAGS="-D_FORTIFY_SOURCE=2"
CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
-fno-plt"
CXXFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fstack-protector-strong
-fno-plt"
LDFLAGS="-Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now"
#-- Make Flags: change this for DistCC/SMP systems
#MAKEFLAGS="-j2"
#-- Debugging flags
DEBUG_CFLAGS="-g -fvar-tracking-assignments"
DEBUG_CXXFLAGS="-g -fvar-tracking-assignments"

--------------------------------------------------

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

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

  parent reply	other threads:[~2017-07-26 19:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-17 16:02 [Bug 101484] [bisected, SI] Steam fails to render content bugzilla-daemon
2017-06-19 23:48 ` bugzilla-daemon
2017-06-19 23:49 ` bugzilla-daemon
2017-06-20  6:11 ` bugzilla-daemon
2017-06-25  9:06 ` bugzilla-daemon
2017-06-25 10:37 ` [Bug 101484] [bisected] Steam fails to render content, if mesa is compiled with -O2 bugzilla-daemon
2017-06-25 10:40 ` bugzilla-daemon
2017-06-25 10:51 ` bugzilla-daemon
2017-06-25 12:25 ` [Bug 101484] [regression, bisected] Steam fails to render content, if mesa is compiled with -O2 -march=haswell bugzilla-daemon
2017-06-25 17:19 ` bugzilla-daemon
2017-06-26  9:05 ` bugzilla-daemon
2017-06-26  9:07 ` bugzilla-daemon
2017-06-27  9:03 ` bugzilla-daemon
2017-07-08 16:17 ` bugzilla-daemon
2017-07-26 19:30 ` bugzilla-daemon [this message]
2017-07-30  1:52 ` bugzilla-daemon
2017-08-06 18:54 ` [Bug 101484] [regression, bisected] Steam fails to render content, if mesa is compiled with -O2 -march=native (CPU with bmi instruction supported) bugzilla-daemon
2017-08-08 15:11 ` bugzilla-daemon
2018-01-21 19:20 ` 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-101484-502-FD6fIxXR8e@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).