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] Remove code disabled since at least 1999 from lookup_struct_elt_type. Date: Tue, 12 Mar 2019 22:06:00 -0000 [thread overview] Message-ID: <36c53a0262f84ad11d738471789dadfa9c4eb320@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 36c53a0262f84ad11d738471789dadfa9c4eb320 *** Author: John Baldwin <jhb@FreeBSD.org> Branch: master Commit: 36c53a0262f84ad11d738471789dadfa9c4eb320 Remove code disabled since at least 1999 from lookup_struct_elt_type. Update the comment above the function to reflect the code removal and document the existing behavior. gdb/ChangeLog: * gdbtypes.c (lookup_struct_elt_type): Update comment and remove disabled code block.
next reply other threads:[~2019-03-12 22:06 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-03-12 22:06 sergiodj+buildbot [this message] 2019-03-12 22:06 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2019-03-13 12:15 ` Failures on Debian-s390x-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-03-13 12:46 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2019-03-13 13:04 ` Failures on Debian-s390x-m64, " sergiodj+buildbot 2019-03-14 14:29 ` Failures on Fedora-i686, " sergiodj+buildbot 2019-03-14 15:38 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2019-03-14 15:40 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2019-03-14 15:54 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2019-03-14 16:15 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2019-03-14 16:24 ` Failures on Fedora-x86_64-native-gdbserver-m32, " 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=36c53a0262f84ad11d738471789dadfa9c4eb320@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).