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] PR24061, powerpc-ibm-aix-ar sets bogus file permissions when extracting Date: Fri, 04 Jan 2019 02:21:00 -0000 [thread overview] Message-ID: <677bd4c69d0eda4f2ae635d793f23c0b1413a9e9@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 677bd4c69d0eda4f2ae635d793f23c0b1413a9e9 *** Author: Alan Modra <amodra@gmail.com> Branch: master Commit: 677bd4c69d0eda4f2ae635d793f23c0b1413a9e9 PR24061, powerpc-ibm-aix-ar sets bogus file permissions when extracting Mode field should be read in octal, all the rest in decimal. Do so. PR 24061 PR 21786 * coff-rs6000.c (GET_VALUE_IN_FIELD): Add base parameter and adjust all callers. (EQ_VALUE_IN_FIELD): Likewise. * coff64-rs6000.c (GET_VALUE_IN_FIELD): Likewise.
next reply other threads:[~2019-01-04 2:21 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-04 2:21 sergiodj+buildbot [this message] 2019-01-04 2:21 ` Failures on RHEL-s390x-m64, branch master sergiodj+buildbot 2019-01-04 13:10 ` Failures on Debian-s390x-native-gdbserver-m64, " sergiodj+buildbot 2019-01-04 15:05 ` Failures on Fedora-i686, " sergiodj+buildbot 2019-01-04 15:49 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " sergiodj+buildbot 2019-01-04 16:01 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-01-04 16:07 ` Failures on Fedora-x86_64-native-gdbserver-m64, " sergiodj+buildbot 2019-01-04 16:14 ` Failures on Fedora-x86_64-m64, " sergiodj+buildbot 2019-01-04 16:23 ` Failures on Fedora-x86_64-m32, " sergiodj+buildbot 2019-01-04 16:57 ` Failures on Fedora-x86_64-native-gdbserver-m32, " sergiodj+buildbot 2019-01-06 2:42 ` Failures on Ubuntu-Aarch64-native-extended-gdbserver-m64, " sergiodj+buildbot 2019-01-06 4:16 ` Failures on Ubuntu-Aarch64-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=677bd4c69d0eda4f2ae635d793f23c0b1413a9e9@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).