[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2019-09-18 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

GitLab Migration User  changed:

   What|Removed |Added

 Status|NEW |RESOLVED
 Resolution|--- |MOVED

--- Comment #17 from GitLab Migration User  ---
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been
closed from further activity.

You can subscribe and participate further through the new bug through this link
to our GitLab instance: https://gitlab.freedesktop.org/mesa/mesa/issues/144.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev

[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-10-24 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

--- Comment #16 from Stuart Young  ---
There's a fix for this in the Debian experimental package for libclc. If you
haven't already done so and this bug affects you, please test and give feedback
on the Debian bug.

Related links:
 Tracker: https://tracker.debian.org/pkg/libclc
 Pkg change detail:
https://tracker.debian.org/news/994503/accepted-libclc-020git20180917-2-source-into-experimental/
 Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=904718

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-10-21 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

--- Comment #15 from Jan Vesely  ---
(In reply to infinity0 from comment #14)
> Did you get a chance to analyze my dump?
> 
> I filed a LLVM bug here https://bugs.llvm.org/show_bug.cgi?id=38979
> 
> Didn't yet get a chance to test it with LLVM 7 yet but I didn't manage to
> find any related bugs in their tracker so perhaps nobody fixed it yet.

Hi,

sorry for the late reply. given the already strained time/resources, this is
not a priority. The fix to this bug is for Debian to stop modifying libclc
cflags.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-09-17 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

--- Comment #14 from infini...@pwned.gg ---
Did you get a chance to analyze my dump?

I filed a LLVM bug here https://bugs.llvm.org/show_bug.cgi?id=38979

Didn't yet get a chance to test it with LLVM 7 yet but I didn't manage to find
any related bugs in their tracker so perhaps nobody fixed it yet.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-09-11 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

Timothy Arceri  changed:

   What|Removed |Added

  Component|Other   |Gallium/StateTracker/Clover

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-07-31 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

--- Comment #13 from infini...@pwned.gg ---
Created attachment 140907
  --> https://bugs.freedesktop.org/attachment.cgi?id=140907=edit
clover debug dump

Attached a dump, it's 1 out of several thousand files and compressed is 11MB.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-07-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

--- Comment #12 from Gian-Carlo Pascutto  ---
So the bugs are:

1) Debian adding flags even if they don't make sense (i.e. stack protection on
GPU code). Should be filed in Debian against libclc.

2) LLVM respecting that flag even if it shouldn't. Should be checked if it
still happens with LLVM 7 and filed against LLVM if so.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-07-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

--- Comment #11 from Jan Vesely  ---
GPUs don't really have a stack (not for data anyway) and AMDGCN backend
currently inlines all function calls anyway.
I'm not sure what kind of checks the flag adds.
If anyone can upload the different libclc bitcode it should be easy to spot.
My guess would be that it adds some initialized global variables used in
internal checks. This is illegal in CLC. only variables in constant address
space can have initializers.

IMO Debian should not be arbitrarily adding compilation flags unless they know
what they're doing and they have tested the resulting package.

local variables are stored in private address space which is backed either by
register file, or private buffers.
using volatile, to control where it is located, is a rather hacky workaround of
suboptimal register allocation/instruction scheduling.
Reporting a llvm bug with a reproducer can help. it'd need to be reproducible
using llvm-7, there are no further releases of llvm-5 or 6 planned.

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev


[Mesa-dev] [Bug 107369] "volatile" in OpenCL code not recognized when compiling with -fstack-protector

2018-07-27 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=107369

Gian-Carlo Pascutto  changed:

   What|Removed |Added

Summary|"volatile" in OpenCL code   |"volatile" in OpenCL code
   |not recognized by POLARIS10 |not recognized when
   |and KABINI  |compiling with
   ||-fstack-protector

--- Comment #10 from Gian-Carlo Pascutto  ---
infini

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.___
mesa-dev mailing list
mesa-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/mesa-dev