This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug target/69890] FAIL: gcc.target/i386/chkp-* on x86_64-apple-darwin15


https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69890

--- Comment #4 from Ilya Enkovich <ienkovich at gcc dot gnu.org> ---
(In reply to Dominique d'Humieres from comment #3)
> --- ../_clean/gcc/testsuite/gcc.target/i386/chkp-strlen-1.c	2016-01-20
> 19:08:43.000000000 +0100
> +++ gcc/testsuite/gcc.target/i386/chkp-strlen-1.c	2016-03-29
> 17:25:30.000000000 +0200
> @@ -1,6 +1,6 @@
>  /* { dg-do compile { target { ! x32 } } } */
>  /* { dg-options "-fcheck-pointer-bounds -mmpx -O2 -fdump-tree-strlen" } */
> -/* { dg-final { scan-tree-dump "memcpy.chkp" "strlen" } } */
> +/* { dg-final { scan-tree-dump "memcpy(_chk)?.chkp" "strlen" } } */
>  
>  #include "string.h"
>  
> ?
> 
> Now 
> 
> grep memcpy chkp-stropt-1.c.097t.chkpopt 
> 
> gives
>   __builtin___memcpy_chk.chkp (buf1_2(D), __chkp_bounds_of_buf1_7(D),
> buf2_4(D), __chkp_bounds_of_buf2_8(D), len_5(D), 18446744073709551615);
> 
> What should I do for that?

Well, tests were not supposed to check object_sizes pass capabilities.  But
allowing misoptimized code means we don't test functionality we wanted to test.
 I think these tests may use __builtin_* versions of string functions to make
tests independent from headers.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]