public inbox for gdb-testers@sourceware.org help / color / mirror / Atom feed
From: gdb-buildbot@sergiodj.net To: gdb-testers@sourceware.org Subject: [binutils-gdb] Sync config with GCC Date: Wed, 10 Jun 2020 20:20:29 -0400 [thread overview] Message-ID: <56770bdab2585be4d3171b3512d2167106dca53e@gdb-build> (raw) *** TEST RESULTS FOR COMMIT 56770bdab2585be4d3171b3512d2167106dca53e *** commit 56770bdab2585be4d3171b3512d2167106dca53e Author: H.J. Lu <hjl.tools@gmail.com> AuthorDate: Sat May 16 06:07:12 2020 -0700 Commit: H.J. Lu <hjl.tools@gmail.com> CommitDate: Sat May 16 06:07:12 2020 -0700 Sync config with GCC Sync with GCC 2020-05-15 H.J. Lu <hongjiu.lu@intel.com> PR bootstrap/95147 * cet.m4 (GCC_CET_FLAGS): Also check if -fcf-protection works when defaulting to auto. 2020-05-14 H.J. Lu <hongjiu.lu@intel.com> * cet.m4 (GCC_CET_FLAGS): Change default to auto. diff --git a/config/ChangeLog b/config/ChangeLog index de8c327b54..0e988b19c9 100644 --- a/config/ChangeLog +++ b/config/ChangeLog @@ -1,3 +1,16 @@ +2020-05-16 H.J. Lu <hongjiu.lu@intel.com> + + Sync with GCC + 2020-05-15 H.J. Lu <hongjiu.lu@intel.com> + + PR bootstrap/95147 + * cet.m4 (GCC_CET_FLAGS): Also check if -fcf-protection works + when defaulting to auto. + + 2020-05-14 H.J. Lu <hongjiu.lu@intel.com> + + * cet.m4 (GCC_CET_FLAGS): Change default to auto. + 2020-05-12 H.J. Lu <hongjiu.lu@intel.com> Sync with GCC diff --git a/config/cet.m4 b/config/cet.m4 index d9608699cd..2bb2c8a95a 100644 --- a/config/cet.m4 +++ b/config/cet.m4 @@ -3,7 +3,7 @@ dnl GCC_CET_FLAGS dnl (SHELL-CODE_HANDLER) dnl AC_DEFUN([GCC_CET_FLAGS],[dnl -GCC_ENABLE(cet, no, ,[enable Intel CET in target libraries], +GCC_ENABLE(cet, auto, ,[enable Intel CET in target libraries], permit yes|no|auto) AC_MSG_CHECKING([for CET support]) @@ -13,6 +13,8 @@ case "$host" in auto) # Check if target supports multi-byte NOPs # and if assembler supports CET insn. + save_CFLAGS="$CFLAGS" + CFLAGS="$CFLAGS -fcf-protection" AC_COMPILE_IFELSE( [AC_LANG_PROGRAM( [], @@ -25,6 +27,7 @@ asm ("setssbsy"); ])], [enable_cet=yes], [enable_cet=no]) + CFLAGS="$save_CFLAGS" ;; yes) # Check if assembler supports CET.
next reply other threads:[~2020-06-11 0:20 UTC|newest] Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-11 0:20 gdb-buildbot [this message] 2020-06-11 0:20 ` Failures on Fedora-i686, branch master gdb-buildbot 2020-06-11 0:40 ` Failures on Fedora-x86_64-cc-with-index, " gdb-buildbot 2020-06-11 0:54 ` Failures on Fedora-x86_64-m32, " gdb-buildbot 2020-06-11 1:15 ` Failures on Fedora-x86_64-m64, " gdb-buildbot 2020-06-11 1:41 ` Failures on Fedora-x86_64-native-extended-gdbserver-m32, " gdb-buildbot 2020-06-11 1:59 ` Failures on Fedora-x86_64-native-extended-gdbserver-m64, " gdb-buildbot 2020-06-11 2:58 ` Failures on Fedora-x86_64-native-gdbserver-m32, " gdb-buildbot 2020-06-11 3:16 ` Failures on Fedora-x86_64-native-gdbserver-m64, " gdb-buildbot -- strict thread matches above, loose matches on Subject: below -- 2015-07-27 15:06 [binutils-gdb] Sync config with GCC 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=56770bdab2585be4d3171b3512d2167106dca53e@gdb-build \ --to=gdb-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).