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] dwarf2read: Restrict ICC workaround to ICC<14 Date: Tue, 26 Sep 2017 18:56:00 -0000 [thread overview] Message-ID: <5230b05a94b964da335a0758686b92a8efcc823d@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 5230b05a94b964da335a0758686b92a8efcc823d *** Author: Walfred Tedeschi <walfred.tedeschi@intel.com> Branch: master Commit: 5230b05a94b964da335a0758686b92a8efcc823d dwarf2read: Restrict ICC workaround to ICC<14 GDB has a workaround for DWARF output by ICC, related to missing DW_AT_declaration on incomplete types. The bug was fixed in ICC 14, so this commit adjusts GDB accordingly. For the version check, this adds a new parser function for the ICC producer string. While at it, it also adds unit tests for the producer parsing covering the new function and preexisting parsers. gdb/ChangeLog: 2017-09-26 Walfred Tedeschi <walfred.tedeschi@intel.com> Pedro Alves <palves@redhat.com> * dwarf2read.c (dwarf2_cu): Remove field producer_is_icc and add producer_is_icc_lt_14. (producer_is_icc_lt_14): New function. (check_producer): Add code for checking version of ICC. (producer_is_icc): Move to producer.c. (read_structure_type): Restrict ICC workaround to ICC<14. * producer.c: Include selftest.h. (producer_is_icc, producer_parsing_tests, _initialize_producer): New functions. * producer.h (producer_is_icc): New declaration.
next reply other threads:[~2017-09-26 18:41 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-09-26 18:56 sergiodj+buildbot [this message] 2017-09-26 18:59 ` Failures on Fedora-s390x-m64, branch master sergiodj+buildbot 2017-09-26 19:39 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2017-09-26 19:41 ` Failures on Fedora-x86_64-cc-with-index, " sergiodj+buildbot 2017-09-26 19:46 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2017-09-26 20:02 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-26 20:10 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-26 20:34 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2017-09-26 23:20 ` Failures on Ubuntu-AArch64-native-gdbserver-m64, " sergiodj+buildbot 2017-09-26 23:51 ` Failures on Ubuntu-AArch64-m64, " sergiodj+buildbot 2017-09-27 4:15 ` Failures on Ubuntu-AArch32-m32, " sergiodj+buildbot 2017-09-27 5:03 ` Failures on Ubuntu-AArch32-native-extended-gdbserver-m32, " sergiodj+buildbot 2017-09-27 6:19 ` Failures on Ubuntu-AArch32-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=5230b05a94b964da335a0758686b92a8efcc823d@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).