public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: sergiodj+buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Hurd, C++: kern_return_t vs. error_t Date: Thu, 08 Dec 2016 10:43:00 -0000 [thread overview] Message-ID: <0947023d1d4b5d8803a1065d622f707010b2bcdc@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 0947023d1d4b5d8803a1065d622f707010b2bcdc *** Author: Thomas Schwinge <thomas@codesourcery.com> Branch: master Commit: 0947023d1d4b5d8803a1065d622f707010b2bcdc Hurd, C++: kern_return_t vs. error_t GNU/Hurd uses its own "typedef enum __error_t_codes error_t;" ([glibc]/sysdeps/mach/hurd/bits/errno.h), contrary to the default "typedef int error_t;" ([glibc]/stdlib/errno.h). The Mach/Hurd RPCs return kern_return_t values, for which, upon assigning them to an error_t variable, GCC in C++ mode tells us "error: invalid conversion from 'kern_return_t {aka int}' to 'error_t {aka __error_t_codes}'". Instead of casting all these RPC return values to "error_t", just use "kern_return_t" variables: gdb/ * gnu-nat.c (proc_get_exception_port, proc_set_exception_port) (INF_RESUME_MSGPORT_RPC, proc_get_state, _proc_get_exc_port) (proc_steal_exc_port, proc_restore_exc_port, make_proc) (inf_startup, inf_set_pid, inf_validate_procinfo) (inf_validate_task_sc, inf_set_traced, inf_validate_procs) (inf_signal, inf_continue, gnu_wait, S_exception_raise_request) (do_mach_notify_dead_name, S_proc_wait_reply) (S_msg_sig_post_untraced_reply, S_msg_sig_post_reply) (port_msgs_queued, gnu_read_inferior, gnu_write_inferior) (gnu_find_memory_regions, steal_exc_port, thread_takeover_sc_cmd) (flush_inferior_icache): Instead of "error_t" use "kern_return_t". * i386-gnu-nat.c (fetch_fpregs, store_fpregs, i386_gnu_dr_get) (i386_gnu_dr_set): Likewise.
next reply other threads:[~2016-12-08 10:24 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-12-08 10:43 sergiodj+buildbot [this message] 2016-12-08 10:25 ` Failures on Fedora-i686, branch master sergiodj+buildbot 2016-12-08 10:47 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2016-12-08 10:53 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2016-12-08 11:16 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-12-08 11:17 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2016-12-08 11:29 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2016-12-14 13:39 ` Failures on Fedora-ppc64be-m64, " sergiodj+buildbot 2016-12-14 15:20 ` Failures on Fedora-ppc64be-native-extended-gdbserver-m64, " sergiodj+buildbot 2016-12-14 15:20 ` Failures on Fedora-ppc64be-native-gdbserver-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=0947023d1d4b5d8803a1065d622f707010b2bcdc@gdb-build \ --to=sergiodj+buildbot@sergiodj.net \ --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).