All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 66847] compilation broken with llvm 3.3
Date: Fri, 12 Jul 2013 11:01:02 +0000	[thread overview]
Message-ID: <bug-66847-502-AbuVDLJKAG@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-66847-502@http.bugs.freedesktop.org/>


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

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

--- Comment #4 from Marc Dietrich <marvin24@gmx.de> ---
You should also remove "or newer". Also "master" isn't the right branch (which
one is the right?). While you are at it, checking for r600 target isn't enough,
because it also needs "host".

I have the feeling that we should disable r600-llvm support in 9.1 release
alltogether. I think it was just for testing anyway and likely unstable/lots of
bugs still. It also saves distros from compiling some experimental version of
llvm.

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

[-- Attachment #1.2: Type: text/html, Size: 1379 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:[~2013-07-12 11:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  9:21 [Bug 66847] New: compilation broken with llvm 3.3 bugzilla-daemon
2013-07-12 10:00 ` [Bug 66847] " bugzilla-daemon
2013-07-12 10:26 ` bugzilla-daemon
2013-07-12 10:48 ` bugzilla-daemon
2013-07-12 11:01 ` bugzilla-daemon [this message]
2013-07-12 12:25 ` bugzilla-daemon
2013-07-12 12:29 ` bugzilla-daemon
2013-07-12 18:39 ` bugzilla-daemon
2013-07-19 15:27 ` 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-66847-502-AbuVDLJKAG@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.