public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "hjagasia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/37485] [graphite] Disconnecting exit edge in process of code generation Date: Fri, 12 Sep 2008 17:01:00 -0000 [thread overview] Message-ID: <20080912165941.25874.qmail@sourceware.org> (raw) In-Reply-To: <bug-37485-12304@http.gcc.gnu.org/bugzilla/> ------- Comment #6 from hjagasia at gcc dot gnu dot org 2008-09-12 16:59 ------- 2008-09-05 Jan Sjodin <jan.sjodin@amd.com> Harsha Jagasia <harsha.jagasia@amd.com> * graphite.c (gmp_cst_to_tree): Moved. (iv_stack_entry_is_constant): New. (iv_stack_entry_is_iv): New. (loop_iv_stack_push): Renamed to loop_iv_stack_push_iv. (loop_iv_stack_insert_constant): New. (loop_iv_stack_pop): Use new datatpype. (loop_iv_stack_get_iv): Same. (loop_iv_stack_get_iv_from_name): Same. (loop_iv_stack_debug): Renamed to debug_loop_iv_stack. (loop_iv_stack_patch_for_consts): New. (loop_iv_stack_remove_constants): New. (graphite_create_new_loop): Use loop_iv_stack_push_iv. (translate_clast): Call loop_iv_stack_patch_for_consts and loop_iv_stack_remove_constants. (gloog): Use new datatype. Redirect construction edge to end block to avoid accidental deletion. (limit_scops): Prevent overlapping scops. * graphite.h (enum iv_stack_entry_kind): New. Tag for data in iv stack entry. (union iv_stack_entry_data): New. Data in iv stack entry. (struct iv_stack_entry): New. Datatype for iv stack entries. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37485
next prev parent reply other threads:[~2008-09-12 17:01 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2008-09-11 20:04 [Bug c/37485] New: " harsha dot jagasia at amd dot com 2008-09-11 20:07 ` [Bug middle-end/37485] " harsha dot jagasia at amd dot com 2008-09-12 12:57 ` grosser at gcc dot gnu dot org 2008-09-12 15:44 ` hjagasia at gcc dot gnu dot org 2008-09-12 15:46 ` hjagasia at gcc dot gnu dot org 2008-09-12 16:54 ` hjagasia at gcc dot gnu dot org 2008-09-12 16:56 ` hjagasia at gcc dot gnu dot org 2008-09-12 17:01 ` hjagasia at gcc dot gnu dot org [this message] 2008-09-13 12:44 ` rguenth at gcc dot gnu dot org 2008-09-29 13:23 ` grosser at gcc dot gnu dot org 2008-09-29 14:52 ` spop at gcc dot gnu dot org 2008-10-02 22:51 ` spop at gcc dot gnu dot org 2008-10-03 20:30 ` spop at gcc dot gnu dot org 2008-10-11 2:47 ` grosser at gcc dot gnu dot org 2008-10-11 19:28 ` spop at gcc dot gnu dot org 2008-10-15 16:27 ` spop at gcc dot gnu dot org 2008-10-15 16:29 ` spop at gcc dot gnu dot org
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=20080912165941.25874.qmail@sourceware.org \ --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).