public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
* [Bug sanitizer/59068] libsanitizer doesn't build on x86_64-unknown-linux-gnu with Linux 2.6.18
[not found] <bug-59068-4@http.gcc.gnu.org/bugzilla/>
@ 2013-12-03 5:55 ` kcc at gcc dot gnu.org
2014-04-21 5:34 ` y.gribov at samsung dot com
2020-09-08 12:08 ` fxcoudert at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: kcc at gcc dot gnu.org @ 2013-12-03 5:55 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59068
--- Comment #1 from Kostya Serebryany <kcc at gcc dot gnu.org> ---
>From another discussion
(http://gcc.gnu.org/ml/gcc-patches/2013-12/msg00174.html):
I suggest to simply disable libsanitizer build on the older systems
which is what happens de facto now.
If there is significant interest in maintaining asan&co on older
systems (which I have not seen so far),
then those interested will need to help us in upstream repository (llvm) by
a) sending us patches using http://llvm.org/docs/Phabricator.html and
b) setting up a public buildbot (attached to the LLVM master bot) with
the system they care about.
If there is no one interested enough to do a) and b) I say we should
not spend time on this.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug sanitizer/59068] libsanitizer doesn't build on x86_64-unknown-linux-gnu with Linux 2.6.18
[not found] <bug-59068-4@http.gcc.gnu.org/bugzilla/>
2013-12-03 5:55 ` [Bug sanitizer/59068] libsanitizer doesn't build on x86_64-unknown-linux-gnu with Linux 2.6.18 kcc at gcc dot gnu.org
@ 2014-04-21 5:34 ` y.gribov at samsung dot com
2020-09-08 12:08 ` fxcoudert at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: y.gribov at samsung dot com @ 2014-04-21 5:34 UTC (permalink / raw)
To: gcc-bugs
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59068
Yury Gribov <y.gribov at samsung dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |y.gribov at samsung dot com
--- Comment #3 from Yury Gribov <y.gribov at samsung dot com> ---
(In reply to Kostya Serebryany from comment #1)
> From another discussion
> (http://gcc.gnu.org/ml/gcc-patches/2013-12/msg00174.html):
>
> I suggest to simply disable libsanitizer build on the older systems
> which is what happens de facto now.
Sounds like a simple check for minimum kernel version in libsanitizer configure
would do the trick. Can anyone suggest a reliable way to obtain version of
target kernel? We need something that would work all the way back to 2.x
kernels.
^ permalink raw reply [flat|nested] 3+ messages in thread
* [Bug sanitizer/59068] libsanitizer doesn't build on x86_64-unknown-linux-gnu with Linux 2.6.18
[not found] <bug-59068-4@http.gcc.gnu.org/bugzilla/>
2013-12-03 5:55 ` [Bug sanitizer/59068] libsanitizer doesn't build on x86_64-unknown-linux-gnu with Linux 2.6.18 kcc at gcc dot gnu.org
2014-04-21 5:34 ` y.gribov at samsung dot com
@ 2020-09-08 12:08 ` fxcoudert at gcc dot gnu.org
2 siblings, 0 replies; 3+ messages in thread
From: fxcoudert at gcc dot gnu.org @ 2020-09-08 12:08 UTC (permalink / raw)
To: gcc-bugs
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=59068
Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|NEW |RESOLVED
--- Comment #4 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> ---
I am not having this issue anymore.
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-09-08 12:08 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
[not found] <bug-59068-4@http.gcc.gnu.org/bugzilla/>
2013-12-03 5:55 ` [Bug sanitizer/59068] libsanitizer doesn't build on x86_64-unknown-linux-gnu with Linux 2.6.18 kcc at gcc dot gnu.org
2014-04-21 5:34 ` y.gribov at samsung dot com
2020-09-08 12:08 ` fxcoudert at gcc dot gnu.org
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 read-only IMAP folder(s) and NNTP newsgroup(s).