Luis Machado 8ce7415353 Force language to C in gdb.compile/compile-ifunc.exp ... Due to the lack of debug information in the binary, GDB is unable to figure out what language is being used. This may be a problem when doing remote debugging and the binary stops at the entry point containing asm code. In this case GDB will switch to asm as current language and will not switch back to C when it reaches main, which in turn causes the compile feature check to malfunction. This is solved by forcing the language to C after reaching main. gdb/testsuite/ChangeLog: 2015-08-26 Luis Machado <lgustavo@codesourcery.com> * gdb.compile/compile-ifunc.exp (with_test_prefix): Force language to C.		2015-08-27 01:49:05 -03:00
..
compile-constvar.c
compile-constvar.S
compile-ifunc.c
compile-ifunc.exp	Force language to C in gdb.compile/compile-ifunc.exp	2015-08-27 01:49:05 -03:00
compile-mod.c
compile-nodebug.c
compile-ops.c
compile-ops.exp
compile-print.c
compile-print.exp	compile-print.exp: xfail->kfail for '@' GDB array operator	2015-06-04 21:35:43 +02:00
compile-setjmp-mod.c
compile-setjmp.c
compile-setjmp.exp
compile-shlib.c
compile-tls.c
compile-tls.exp
compile.c	compile: Warn for old GCC on cv-qualified self-reference	2015-07-08 14:42:19 +02:00
compile.exp	compile: Warn for old GCC on cv-qualified self-reference	2015-07-08 14:42:19 +02:00
Makefile.in