public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Martin Sebor <msebor@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-7038] Adjust warn_access pass placement [PR104260]. Date: Thu, 3 Feb 2022 21:53:42 +0000 (GMT) [thread overview] Message-ID: <20220203215342.3E33B3858C20@sourceware.org> (raw) https://gcc.gnu.org/g:5a668ec0339c28b0725ded1e80d3276edb76b8b3 commit r12-7038-g5a668ec0339c28b0725ded1e80d3276edb76b8b3 Author: Martin Sebor <msebor@redhat.com> Date: Thu Feb 3 14:51:46 2022 -0700 Adjust warn_access pass placement [PR104260]. Resolves: PR middle-end/104260 - Misplaced waccess3 pass gcc/ChangeLog: PR middle-end/104260 * passes.def (pass_warn_access): Adjust pass placement. Diff: --- gcc/passes.def | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/gcc/passes.def b/gcc/passes.def index 3e75de46c23..f7718181038 100644 --- a/gcc/passes.def +++ b/gcc/passes.def @@ -60,10 +60,10 @@ along with GCC; see the file COPYING3. If not see NEXT_PASS (pass_warn_printf); NEXT_PASS (pass_warn_nonnull_compare); NEXT_PASS (pass_early_warn_uninitialized); + NEXT_PASS (pass_warn_access, /*early=*/true); NEXT_PASS (pass_ubsan); NEXT_PASS (pass_nothrow); NEXT_PASS (pass_rebuild_cgraph_edges); - NEXT_PASS (pass_warn_access, /*early=*/true); POP_INSERT_PASSES () NEXT_PASS (pass_local_optimization_passes); @@ -428,9 +428,9 @@ along with GCC; see the file COPYING3. If not see NEXT_PASS (pass_gimple_isel); NEXT_PASS (pass_harden_conditional_branches); NEXT_PASS (pass_harden_compares); + NEXT_PASS (pass_warn_access, /*early=*/false); NEXT_PASS (pass_cleanup_cfg_post_optimizing); NEXT_PASS (pass_warn_function_noreturn); - NEXT_PASS (pass_warn_access, /*early=*/false); NEXT_PASS (pass_expand);
reply other threads:[~2022-02-03 21:53 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220203215342.3E33B3858C20@sourceware.org \ --to=msebor@gcc.gnu.org \ --cc=gcc-cvs@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).