public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@redhat.com To: gdb-testers@sourceware.org Subject: [binutils-gdb] compile: New 'compile print' Date: Sat, 16 May 2015 15:07:00 -0000 [thread overview] Message-ID: <36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2@kwanyin> (raw) *** TEST RESULTS FOR COMMIT 36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2 *** Author: Jan Kratochvil <jan.kratochvil@redhat.com> Branch: master Commit: 36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2 compile: New 'compile print' It is planned the existing GDB command 'print' will be able to evaluate its expressions using the compiler. There will be some option to choose between the existing GDB evaluation and the compiler evaluation. But as an intermediate step this patch provides the expression printing feature as a new command. I can imagine it could be also called 'maintenance compile print' as in the future one should be able to use its functionality by the normal 'print' command. There was a discussion with Eli about the command name: https://sourceware.org/ml/gdb-patches/2015-03/msg00880.html As there were no other comments yet I haven't renamed it yet, before there is some confirmation about settlement on the final name. Support for the GDB '@' operator to create arrays has been submitted for GCC: [gcc patch] libcc1: '@' GDB array operator https://gcc.gnu.org/ml/gcc-patches/2015-03/msg01451.html gdb/ChangeLog 2015-05-16 Jan Kratochvil <jan.kratochvil@redhat.com> Phil Muldoon <pmuldoon@redhat.com> * NEWS (Changes since GDB 7.9): Add compile print. * compile/compile-c-support.c (add_code_header, add_code_footer) (c_compute_program): Add COMPILE_I_PRINT_ADDRESS_SCOPE and COMPILE_I_PRINT_VALUE_SCOPE. * compile/compile-internal.h (COMPILE_I_PRINT_OUT_ARG_TYPE) (COMPILE_I_PRINT_OUT_ARG, COMPILE_I_EXPR_VAL, COMPILE_I_EXPR_PTR_TYPE): New. * compile/compile-object-load.c: Include block.h. (get_out_value_type): New function. (compile_object_load): Handle COMPILE_I_PRINT_ADDRESS_SCOPE and COMPILE_I_PRINT_VALUE_SCOPE. Set compile_module's OUT_VALUE_ADDR and OUT_VALUE_TYPE. * compile/compile-object-load.h (struct compile_module): Add fields out_value_addr and out_value_type. * compile/compile-object-run.c: Include valprint.h and compile.h. (struct do_module_cleanup): Add fields out_value_addr and out_value_type. (do_module_cleanup): Handle COMPILE_I_PRINT_ADDRESS_SCOPE and COMPILE_I_PRINT_VALUE_SCOPE. (compile_object_run): Propagate out_value_addr and out_value_type. Pass OUT_VALUE_ADDR. * compile/compile.c: Include valprint.h. (compile_print_value, compile_print_command): New functions. (eval_compile_command): Handle failed COMPILE_I_PRINT_ADDRESS_SCOPE. (_initialize_compile): Update compile code help text. Install compile_print_command. * compile/compile.h (compile_print_value): New prototype. * defs.h (enum compile_i_scope_types): Add COMPILE_I_PRINT_ADDRESS_SCOPE and COMPILE_I_PRINT_VALUE_SCOPE. gdb/doc/ChangeLog 2015-05-16 Jan Kratochvil <jan.kratochvil@redhat.com> * gdb.texinfo (Compiling and Injecting Code): Add compile print. gdb/testsuite/ChangeLog 2015-05-16 Jan Kratochvil <jan.kratochvil@redhat.com> * gdb.compile/compile-print.c: New file. * gdb.compile/compile-print.exp: New file.
next reply other threads:[~2015-05-16 15:07 UTC|newest] Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-05-16 15:07 sergiodj+buildbot [this message] 2015-05-16 15:07 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2015-05-16 15:20 ` Failures on Fedora-ppc64be-cc-with-index, " sergiodj+buildbot 2015-05-16 15:24 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2015-05-16 15:28 ` Failures on Fedora-ppc64be-native-gdbserver-m64, " sergiodj+buildbot 2015-05-16 16:14 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-16 17:29 ` Failures on Debian-i686, " sergiodj+buildbot 2015-05-16 17:45 ` Failures on Debian-i686-native-gdbserver, " sergiodj+buildbot 2015-05-16 18:10 ` Failures on Debian-i686-native-extended-gdbserver, " sergiodj+buildbot 2015-05-16 20:08 ` Failures on Debian-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-16 20:14 ` Failures on Debian-x86_64-m64, " sergiodj+buildbot 2015-05-16 20:20 ` Failures on Debian-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-05-16 22:49 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2015-05-16 22:55 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2015-05-16 23:03 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2015-05-16 23:10 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-16 23:18 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2015-05-16 23:25 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2015-05-16 23:32 ` Failures on Fedora-x86_64-cxx-build-m64, " sergiodj+buildbot 2015-05-16 23:38 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2015-05-17 7:04 ` Failures on Fedora-ppc64le-native-extended-gdbserver-m64, " sergiodj+buildbot 2015-05-17 7:12 ` Failures on Fedora-ppc64le-cc-with-index, " sergiodj+buildbot 2015-05-17 7:18 ` Failures on Fedora-ppc64le-native-gdbserver-m64, " sergiodj+buildbot 2015-05-17 7:24 ` Failures on Fedora-ppc64le-m64, " sergiodj+buildbot
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=36de76f9cc2eea0bd5f1b7ce74ef60e1aa0b27c2@kwanyin \ --to=sergiodj+buildbot@redhat.com \ --cc=gdb-testers@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
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).