> gsi_insert_seq_before Yes, I discovered this myself via Google and ironically it was because of a 2008 comment by you that you'd renamed gsi_link_seq_before. Frankly, I find this a bit amusing. This doesn't seem to be a very heavily used function and I'm probably going to be its user.
Gary ________________________________ From: Richard Biener <richard.guent...@gmail.com> Sent: Thursday, October 22, 2020 11:01 PM To: Gary Oblock <g...@amperecomputing.com> Cc: gcc@gcc.gnu.org <gcc@gcc.gnu.org> Subject: Re: Missing functionality [EXTERNAL EMAIL NOTICE: This email originated from an external sender. Please be mindful of safe email handling and proprietary information protection practices.] On Fri, Oct 23, 2020 at 5:10 AM Gary Oblock via Gcc <gcc@gcc.gnu.org> wrote: > > I'm finishing up coding my patterns for the structure reorganization > optimization. They recognize certain instructions and replace them > other instructions. I've got some code that generates gimple which is > inserted as it's created with gsi_insert_before. This code is > something I'd like to use at other points in my optimization so I'd > like to create a function to do this. > > Now comes the interesting bit. I'd like to use gimple sequences and > after reading the internals documentation I put together something > using gimple_seq_add_stmt to add the generated gimple to a new > sequence. After this I tried inserting the sequence into the basic > block's sequence with gsi_link_seq_before. It turns out there is no > gsi_link_seq_before! I could probably write one myself but that begs > the question, why is there no gsi_link_seq_before and what should I > use instead? gsi_insert_seq_before > Thank > > Gary > > > CONFIDENTIALITY NOTICE: This e-mail message, including any attachments, is > for the sole use of the intended recipient(s) and contains information that > is confidential and proprietary to Ampere Computing or its subsidiaries. It > is to be used solely for the purpose of furthering the parties' business > relationship. Any unauthorized review, copying, or distribution of this email > (or any attachments thereto) is strictly prohibited. If you are not the > intended recipient, please contact the sender immediately and permanently > delete the original and any copies of this email and any attachments thereto.
