From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 104607] Mesa fails to build in OBS after c797cd605ac9cb42795a40b1967b6dd10184b763
Date: Sat, 31 Mar 2018 23:53:28 +0000 [thread overview]
Message-ID: <bug-104607-502-RlToD8n3Cm@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-104607-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1072 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=104607
Timothy Arceri <t_arceri@yahoo.com.au> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #3 from Timothy Arceri <t_arceri@yahoo.com.au> ---
Fixed by:
author Mauro Rossi <issor.oruam@gmail.com>
commit 4d61eb80187cd8e5984eed94f2ae3c7d6c3b3aa0 (patch)
ac: fix build error in si_shader
assert() is replaced by unreachable(), to avoid following building error:
external/mesa/src/gallium/drivers/radeonsi/si_shader.c:1967:1:
error: control may reach end of non-void function [-Werror,-Wreturn-type]
}
^
1 error generated.
Fixes: c797cd6 ("ac: add load_patch_vertices_in() to the abi")
Reviewed-by: Bas Nieuwenhuizen <bas@basnieuwenhuizen.nl>
Reviewed-by: Timothy Arceri <tarceri@itsqueeze.com>
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2835 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
prev parent reply other threads:[~2018-03-31 23:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-12 18:39 [Bug 104607] Mesa fails to build in OBS after c797cd605ac9cb42795a40b1967b6dd10184b763 bugzilla-daemon
2018-01-12 18:43 ` bugzilla-daemon
2018-01-12 19:22 ` bugzilla-daemon
2018-03-31 23:53 ` bugzilla-daemon [this message]
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-104607-502-RlToD8n3Cm@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.