https://bugs.freedesktop.org/show_bug.cgi?id=93103
GitLab Migration User changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=93103
Adam Jackson changed:
What|Removed |Added
Component|Drivers/X11 |Drivers/Gallium/llvmpipe
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #17 from fiach.an...@gmail.com ---
I've run into a variant of this bug where when using swrast, symbols from a
shared object linked by LLVM (libedit) conflict with symbols from a shared
object used by a client application
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #16 from fiach.an...@gmail.com ---
Created attachment 128707
--> https://bugs.freedesktop.org/attachment.cgi?id=128707=edit
Test-case for global symbol contamination due to LLVM dependency.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=93103
Vedran Miletić changed:
What|Removed |Added
CC||ved...@miletic.net
https://bugs.freedesktop.org/show_bug.cgi?id=93103
Jan Ziak <0xe2.0x9a.0...@gmail.com> changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #15 from Emil Velikov ---
The commit mentioned addresses only their autoconf (more like gnumake really)
build. Current upstream covers both builds with should be identical
auto-generated (?) LD version
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #14 from Michel Dänzer ---
FWIW, IME LLVM's symbol versioning seems to only help if all LLVM libraries
involved have versioned symbols. I did verify at one point with gambas that
radeonsi using a different LLVM
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #5 from Tobias Schlüter ---
Thank you for the quick response! I'll take the comments to mean that this
shouldn't happen with very recent versions of libmesa and llvm. It does happen
with fairly recent versions
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #6 from Emil Velikov ---
(In reply to Tobias Schlüter from comment #5)
> Thank you for the quick response! I'll take the comments to mean that this
> shouldn't happen with very recent versions of libmesa
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #7 from Jose Fonseca ---
I wonder if Tobias is using XLIB-based libGL.so.1, as opposed to the DRI based
libGL.so.1.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #8 from Emil Velikov ---
(In reply to Jose Fonseca from comment #7)
> I wonder if Tobias is using XLIB-based libGL.so.1, as opposed to the DRI
> based libGL.so.1.
I fixed that one got around mesa 10.3 - see
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #9 from Jose Fonseca ---
(In reply to Emil Velikov from comment #6)
> Check, if ever in doubt about the exposed symbols.
>
> libGL itself
> $ nm -CD --defined-only /lib/libGL.so | grep -v " gl"
[...]
>
> DRI
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #10 from Tobias Schlüter ---
Probably no longer relevant per #8, and I don't know how to tell different
libGL.so.1 apart with certainty, but I guess you can do this based on ldd
output, so here goes (DRI appears,
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #11 from Emil Velikov ---
(In reply to Jose Fonseca from comment #9)
> $ nm -CD --defined-only /usr/lib/x86_64-linux-gnu/libLLVM-3.6.so.1
>
> shows lot of them.
>
I have the very vague memory that older
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #12 from Emil Velikov ---
(In reply to Tobias Schlüter from comment #10)
> Probably no longer relevant per #8, and I don't know how to tell different
> libGL.so.1 apart with certainty, but I guess you can do
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #13 from Tobias Schlüter ---
(In reply to Emil Velikov from comment #12)
> (In reply to Tobias Schlüter from comment #10)
> > I have pointed the ROOT people to this bug report, I hope they can draw
> > their
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #2 from Emil Velikov ---
Hmm I'm pretty sure that I removed all of those an year or two ago.
And looking at the patches in said report, it seems that it was a problem on
their end -> they were not hiding
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #3 from Emil Velikov ---
(In reply to Jose Fonseca from comment #1)
> In addition to that, we probably also need to use a LD version script to
> ensure that LLVM symbols don't pop in the dynamic symbol
https://bugs.freedesktop.org/show_bug.cgi?id=93103
Jose Fonseca changed:
What|Removed |Added
CC||jfons...@vmware.com
https://bugs.freedesktop.org/show_bug.cgi?id=93103
Bug ID: 93103
Summary: llvm symbols leak through, cause trouble with software
rendering in llvm-linked software
Product: Mesa
Version: 10.1
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=93103
--- Comment #4 from Michel Dänzer ---
Also note that as of version 3.6, LLVM uses versioned symbols, which may help
for this issue.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the
22 matches
Mail list logo