public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug tree-optimization/35513] Improve targetm.binds_local_p Date: Sat, 12 Feb 2022 13:50:20 +0000 [thread overview] Message-ID: <bug-35513-4-lwnpwyPSCO@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-35513-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=35513 --- Comment #6 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by H.J. Lu <hjl@gcc.gnu.org>: https://gcc.gnu.org/g:5c4258d7c78a92ab17c14dec1163d87fc42ff019 commit r12-7213-g5c4258d7c78a92ab17c14dec1163d87fc42ff019 Author: H.J. Lu <hjl.tools@gmail.com> Date: Thu Feb 10 05:42:49 2022 -0800 x86: Update PR 35513 tests 1. Require linker with GNU_PROPERTY_1_NEEDED support for PR 35513 run-time tests. 2. Compile pr35513-8.c to scan assembly code. PR testsuite/104481 * g++.target/i386/pr35513-1.C: Require property_1_needed target. * g++.target/i386/pr35513-2.C: Likewise. * gcc.target/i386/pr35513-8.c: Change to compile. * lib/target-supports.exp (check_compile): Support assembly code. (check_effective_target_property_1_needed): New proc.
next prev parent reply other threads:[~2022-02-12 13:50 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-35513-4@http.gcc.gnu.org/bugzilla/> 2022-02-09 12:39 ` cvs-commit at gcc dot gnu.org 2022-02-12 13:50 ` cvs-commit at gcc dot gnu.org [this message] 2022-03-01 15:45 ` cvs-commit at gcc dot gnu.org 2008-03-09 15:07 [Bug tree-optimization/35513] New: " hjl dot tools at gmail dot com 2008-03-09 15:17 ` [Bug tree-optimization/35513] " hjl dot tools at gmail dot com 2010-01-06 23:34 ` hjl dot tools at gmail dot com
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=bug-35513-4-lwnpwyPSCO@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.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).