Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread enh
On Fri, Aug 15, 2014 at 1:05 PM, Alexander Ivchenko wrote: > 2014-08-15 21:32 GMT+04:00 enh : >> can you file bugs against bionic for stuff like this? use >> b.android.com (and feel free to mail me to ensure that they get >> noticed). > > Sure, I will do that. > >> one thing we'd like to do is get

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread Alexander Ivchenko
2014-08-15 21:32 GMT+04:00 enh : > can you file bugs against bionic for stuff like this? use > b.android.com (and feel free to mail me to ensure that they get > noticed). Sure, I will do that. > one thing we'd like to do is get to a point where we're building > gcc/gdb et cetera without any local

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread enh
On Fri, Aug 15, 2014 at 10:56 AM, Mike Stump wrote: > On Aug 15, 2014, at 10:32 AM, enh wrote: >> can you file bugs against bionic for stuff like this? > > I suspect you meant to ask Alexander this question… but just in case you did > intend to ask me, no. I don’t have any visibility into andr

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread Mike Stump
On Aug 15, 2014, at 10:32 AM, enh wrote: > can you file bugs against bionic for stuff like this? I suspect you meant to ask Alexander this question… but just in case you did intend to ask me, no. I don’t have any visibility into android local patches or procedures. In the end, people with lo

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread enh
can you file bugs against bionic for stuff like this? use b.android.com (and feel free to mail me to ensure that they get noticed). one thing we'd like to do is get to a point where we're building gcc/gdb et cetera without any local hacks, and when we've got to that point, we're going to have to g

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread Mike Stump
On Aug 15, 2014, at 6:49 AM, Alexander Ivchenko wrote: > * lib/target-supports.exp (error_h): New check. > (libc_has_complex_functions): Ditto. > (tgmath_h): Ditto. > * gcc.dg/builtins-59.c: Add libc_has_complex_functions check. > * gcc.dg/builtins-61.c: Likewise. >

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-15 Thread Alexander Ivchenko
Hi Joseph, I seem to address what you've said. Except for I still left non_bionic check for three tests (Namely: builtins-67.c, strlenopt-14g.c, strlenopt-14gf.c) because checks for the presence of mempcpy, stpcpy and rintl (sorry, I didn't mention it last time) seem to be very narrow, I don't t

Re: [patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-13 Thread Joseph S. Myers
On Thu, 14 Aug 2014, Alexander Ivchenko wrote: > Hi, > > This patch disables a bunch of tests that fail when using Bionic libc. > But this is expected; three reasons: > - Bionic does not support complex functions. > - Bionic does not have tgmath.h and error.h headers. > - Bionic does not have mem

[patch, testsuite] Applying non_bionic effective target to particular tests

2014-08-13 Thread Alexander Ivchenko
Hi, This patch disables a bunch of tests that fail when using Bionic libc. But this is expected; three reasons: - Bionic does not support complex functions. - Bionic does not have tgmath.h and error.h headers. - Bionic does not have mempcpy and stpcpy. diff --git a/gcc/testsuite/ChangeLog b/gcc/