public inbox for gcc-cvs@sourceware.org help / color / mirror / Atom feed
From: Trevor Saunders <tbsaunde@gcc.gnu.org> To: gcc-cvs@gcc.gnu.org Subject: [gcc r12-1599] fix get-loop_hot_path with gcc 4.8.5 Date: Thu, 17 Jun 2021 15:12:48 +0000 (GMT) [thread overview] Message-ID: <20210617151248.DF7B5396BC1F@sourceware.org> (raw) https://gcc.gnu.org/g:caeb8892a556a4a634641c7613fec957359dbd49 commit r12-1599-gcaeb8892a556a4a634641c7613fec957359dbd49 Author: Trevor Saunders <tbsaunde@tbsaunde.org> Date: Thu Jun 17 11:10:15 2021 -0400 fix get-loop_hot_path with gcc 4.8.5 gcc/ChangeLog: * cfgloopanal.c (get_loop_hot_path): Make path an auto_vec. Diff: --- gcc/cfgloopanal.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/gcc/cfgloopanal.c b/gcc/cfgloopanal.c index fdd8d3f43fe..2db46c81036 100644 --- a/gcc/cfgloopanal.c +++ b/gcc/cfgloopanal.c @@ -504,7 +504,7 @@ auto_vec<basic_block> get_loop_hot_path (const class loop *loop) { basic_block bb = loop->header; - vec<basic_block> path = vNULL; + auto_vec<basic_block> path; bitmap visited = BITMAP_ALLOC (NULL); while (true)
reply other threads:[~2021-06-17 15:12 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=20210617151248.DF7B5396BC1F@sourceware.org \ --to=tbsaunde@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).